Live data from Hacker News

Viewing profile — nuttingd

nuttingd

HN member
Joined
Sat, May 28, 2016, 5:27 PM UTC
HN karma
40
Public activity
9 items

About nuttingd

Hi! I'm David Nutting from Portland, Oregon, USA.

- https://github.com/nuttingd

Recent public activity

  1. comment
    Comment #41910708

    You would need to use serializable isolation for this to hold true. Any isolation level less than serializable will use the snapshot that was active at the time of the select. In P…

  2. comment
    Comment #41133196

    import my_module This is compatible with `__all__` if you have your code broken down into smaller sub-modules and collect them in the main module as follows: # my_module/__init__.p…

  3. comment
    Comment #39995359

    > which makes a very simple concept vastly more confusing than it needs to be. Agreed. The concepts are all very simple. You can throw away all of the domain-specific terminology a…

  4. comment
    Comment #39993255

    It's the accounting equation being represented in canonical form. A chart of accounts is visualized in the minds of an accountant as: Assets | Liabilities + Equity Accounts classif…

  5. comment
    Comment #38685959

    I have read the docs plenty of times, but it never stuck for me until I read the (free!) PostgreSQL 14 Internals ebook: https://postgrespro.com/community/books/internals Quoted fro…

  6. comment
    Comment #38685267

    One caveat to serializable transactions in Postgres is that ALL concurrent transactions must be running with the SERIALIZABLE isolation level to protect against serialization anoma…

  7. comment
    Comment #38154809

    > (Newspeak “Sprint and Goals”) Sprint "commitments" in my world. A single word with major psychological impacts.

  8. comment
    Comment #38030806

    The check constraint solution isn't a solution to the concurrency issue: it only prevents a negative balance. The balance would still be wrong for the whole range where balance > 0…

  9. comment
    Comment #30649630

    Pagination is harder than it seems to get right. I think pagination is only predictable under these conditions: 1) The offset used for the next fetch must be based on a pointer to …