Live data from Hacker News

Viewing profile — nunwuo

nunwuo

HN member
Joined
Tue, Dec 02, 2014, 10:11 PM UTC
HN karma
34
Public activity
19 items

About nunwuo

No profile information was provided.

Recent public activity

  1. comment
    Comment #21311360

    > So if the driver saw yellow and didn't stop then they can't blame that the red light came too fast because they should be stopped already. Huh? Even if you slam your brakes immed…

  2. comment
    Comment #20667230

    Postgres does this, too; at least to some degree. They call it "synchronized sequential scans".

  3. comment
    Comment #11684328

    > If there is one feature I wish PG had, it is recognizing old format db and offering one command that can in place upgrade damn db, without me googling it every time. So your havi…

  4. comment
    Comment #11635051

    > Closing the connection would cause the client to believe that the file has been fully downloaded - resulting in a truncated file. Not good. That's not correct. Both Content-Lengt…

  5. comment
    Comment #10096939

    > If the query plan in SQLite looks good, it'll stay good. In a real database, you're sitting on a timebomb waiting to go off when autoanalyze ends up running at a bad time. That's…

  6. comment
    Comment #9929216

    > Avoid state at all costs. Stored procedures are stateful. Schema and migrations is pain enough already. What do you mean by that? How is having a bunch of queries in a stored pro…

  7. comment
    Comment #9914635

    And how exactly do you think that will corrupt anything?

  8. comment
    Comment #9914634

    There are no partial updates in 9.5. There likely never will be in Postgres, due to MVCC.

  9. comment
    Comment #9746331

    The good thing about the current name is that there's a clear distinction (at least to users "in the loop") between "psql", the command-line client, and "postgres" the backend serv…

  10. comment
    Comment #9568649

    > Does running the self-pipe trick on a separate thread solve that issue? It seems like it's basically equivalent to signalfd (neither worse nor better, unless you're worried about…

  11. comment
    Comment #9568642

    > 1) You're supposed to set the pipe to be non-blocking. Presumably you also then don't check the return code of the write(2) call in the signal handler. While this solves the case…

  12. comment
    Comment #9409824

    That wouldn't change even if there was a specialized syntax, because of MVCC. So the only problem is that syntactic sugar is lacking, not that the performance isn't as good as it c…

  13. comment
    Comment #9408367

    > If we can address fields with operators (->, ->>, etc.) then why can't those operators modify, too? It works for everything else, after all. It's fairly counter-intuitive from a …

  14. comment
    Comment #9388963

    There is: logical decoding http://www.postgresql.org/docs/9.4/static/logicaldecoding.ht... I wonder why the author chose to waste time on this instead of doing things the proper wa…

  15. comment
    Comment #9381133

    "Lone Ranger"

  16. comment
    Comment #9056884

    Huh? The entire point of listen/notify is exactly that you don't have to poll.

  17. comment
    Comment #8692955

    Untested, but this is the general approach: SELECT unnest(ar).* FROM (SELECT ARRAY(SELECT tbl FROM tbl WHERE .. ORDER BY .. LIMIT 2) AS ar FROM .. OFFSET 0) ss; If you want a speci…

  18. comment
    Comment #8690549

    There's no faith required; the planner is guaranteed not to do that. The "normal" way is to create a composite type containing each of the columns you need, and then "unpack" it to…

  19. comment
    Comment #8690326

    That's not true. Anything you can do with LATERAL you can also do with correlated scalar subqueries in the SELECT list. LATERAL simply makes writing these kinds of queries easier a…