中文 English Français Русский Español العربية

[$] PostgreSQL 19's "scary patch contest"

jzb LWN.net 2026-09-11 01:29 29 views

PostgreSQL 19 was expected to be released in September, in keeping with the database project's longstanding tradition of a major release every year. However, some late-breaking concerns about several of the features slated for inclusion has some developers worried about the quality of the release. On August 25, PostgreSQL contributor Robert Haas sent an email with the subject "scary patch contest" about several patches that have required an unusually large number of bug fixes leading up to the release, which has raised questions about their readiness for a stable release. One of the patches has been reverted, but several are still under heavy revision, and an extra beta release has been slotted in to allow for additional testing.

Read original: https://lwn.net/Articles/1092003/

My Favorites →

← Previous Control GitHub Actions cache access with cache-mode Next → GitHub Copilot is now available in the AI SDK harness layer

Postgres RLS in Symfony: three green isolation tests, and the UPDATE that moves tenant 1's invoices into tenant 2's books

Two articles ago I wrote that the Postgres role which runs your migrations bypasses every row-level security policy. Last week I wrote that with one tenant in the fixture, your isolation suite passes with no policy at all. Both came out of the same comment thread, and by the end of it we had three a

Database 09-14 34 Dev.to (EN Zone)

Turning Mermaid ER diagrams into shareable 3D schema tours

Turning Mermaid ER diagrams into shareable 3D schema tours Mermaid erDiagram is great for docs and PRs. It’s less great when the schema gets dense: boxes overlap, FK lines tangle, and “just zoom out” stops helping. I built Schema3D for that moment: open a Mermaid ER (or SQL / DrawDB) in the brows

Database 09-14 30 DEV Community

finally understand why redis blocks on one slow command, wish I knew this earlier

been learning redis properly for a side project and putting together notes as I go so I actually remember this stuff. always just knew "redis is in memory so it's fast" and left it at that. turns out the part that actually matters is that it runs commands on a single thread. that's not a downside, i

Database 09-14 27 Reddit r/webdev

Tracing Which Internal Consumer Read Each Webhook Event (One Registration, One Queue)

Use one webhook registration, land the payload in a durable queue, and make every internal consumer acknowledge its own copy. That is the least complex design that survives a downstream outage and still answers the question an auditor asks six weeks later: which internal service read which event, un

Database 09-14 29 DEV Community

Comments0

No comments yet — be the first