PostgreSQL 19 Released

(postgresql.org)

135 points | by jkatz05 a day ago ago

12 comments

  • ddxv 20 hours ago ago

    I respect their decision to delay a bit. Looking forward to trying it out.

    Especially this one:

    PostgreSQL 19 adds INSERT ... ON CONFLICT DO SELECT, which lets the RETURNING clause return existing rows that conflict with an insert, simplifying the common "get or create" pattern.

    • nick_ 20 hours ago ago

      Any idea if the select is guaranteed to "see" the conflicting record? For example, if it was deleted "between" the insert failure and the select?

      Update: it looks like yes, at least for basic scenarios (https://dev.to/gabrielanhaia/your-postgres-get-or-create-has...)

    • 6 hours ago ago
      [deleted]
    • borzi 17 hours ago ago

      My agents will be so excited.

      • nextaccountic 14 hours ago ago

        well, then give them a skill just with what's new

        • hologramofham 5 hours ago ago

          I think it depends.. I'd put it in my Claude.md (or one in a folder where my db stuff is, depends on project) so it's definitely always seen.

          Or perhaps memory.

          Probably depends how important it is to do something a certain way and when it decides to.

        • jimbob45 3 hours ago ago

          Are skills not just documentation? Did we really need a new word for documentation? Or am I just an old geezer ranting that thongs go on your feet?

  • perdy 20 hours ago ago

    The ON CONFLICT DO SELECT looks like a good addition, getting the existing row back from RETURNING. No more second SELECT after DO NOTHING.

  • _rwo 5 hours ago ago

    excited about the build-in repack, that took a while

    and thank you pg_repack, it's been a good ride!

  • okc4pardon 20 hours ago ago

    [flagged]

  • vivzkestrel a day ago ago

    [flagged]

    • hans_castorp 20 hours ago ago

      Nothing in those release notes refers to "key value stores"