Over the past month, several major features got reverted from Postgres 19. At this point, even if everything else goes perfectly, Postgres 19 will be released about a month later than originally planned. A couple recent blog posts seem to suggest the reverts happened due to AI finding complex bugs in those patches, with fixes way too invasive this late in the development cycle. I don’t think that narrative matches reality, and I think it matters to correct that.
Database
Tomas Vondra: Are we reverting patches because of bugs found by AI?
Planet PostgreSQL0 views
Source:https://postgr.es/p/9wF
PreviousMing Ying: PlanetScale Released Text Search and We Have a Lot to Say (Part I)NextChris van Eijk: Counting per tenant in PostgreSQL: count, estimate, counter
Related posts
Building an Open-Source RAG Application: What I Learned from Cairnly
0dev.to Machine Learning
Understanding BugSigDB and Its Curation Policy
0dev.to OpenSource

Branch isolation in a live Supabase app
0dev.to Database
LSM-Trees vs B-Trees: Which Side of the Disk You Tax
0dev.to Database
A 9-TiB OLTP Benchmark on PostgreSQL
0dev.to Database
Faster SSDs for PostgreSQL: From Read I/O to WAL Waits
0dev.to Database