Live data from Hacker News

Viewing profile — valgog

valgog

HN member
Joined
Sat, May 09, 2015, 11:26 AM UTC
HN karma
20
Public activity
13 items

About valgog

No profile information was provided.

Recent public activity

  1. story
  2. comment
    Comment #12077606

    This is a very cool SQL SELECT to bash converter to easily parse and analyse data from your CVS files :D

  3. story
  4. story
  5. comment
    Comment #10962191

    Wow, wonderful work! As an additional information about already existing execution plan visualisation tools: Depesz has written the classical PostgreSQL Execution Plan Visualiser y…

  6. comment
    Comment #10882189

    This library makes it really easy to write REST services using python. Saved me a lot of time when doing prototyping of simple (and not so simple) services.

  7. comment
    Comment #10475507

    This library makes it really easy to bootstrap a simple RESTful service with practically no effort. Really nice for prototyping your services.

  8. comment
    Comment #10445086

    Actually stolon is more comparable with Patroni, the core component used by Spilo. One can call Patroni the HA machine, and Spilo an AWS based infrastructure that uses it. So one c…

  9. comment
    Comment #9745039

    Instead of stopping occupation of 3 neighbour nation territories and supporting war machine, they are "freeing" the software. Of cause it is a window of opportunity for the softwar…

  10. comment
    Comment #9741450

    Yes, 100 data model changes are schema changes (that can be one or more table structure change)

  11. comment
    Comment #9741381

    There are definitely a lot of much more interesting videos from PGConf US 2015, especially the one from Robert. My talk was a 'keynote' and not really a conference talk :)

  12. comment
    Comment #9741187

    Actually if you really need to update large JSON documents efficiently, probably the only really efficient technology would be ToroDB http://www.8kdata.com/torodb/

  13. comment
    Comment #9741165

    Actually without providing some benchmark results, the statement, that PostgreSQL has performance problems because of on-copy updating of JSONB, is groundless.