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
Instagram’s new tool for creators targets unauthorized reposts and AI-modified videos
0TechCrunch

150 Shipment Events Entered My Pipeline. Only 146 Made It Through. Here's Why.
0dev.to
MySQL Development as it Happens, Part 2 -Vector Indexes
0Lobsters
Stop Building Franken-Platforms: The 5 Planes of Internal Developer Platform Architecture
0dev.to
Copy several things, then paste them in a different order — without Accessibility permission
0dev.to Productivity
Returning Joined Columns Under Restricted Access in pREST
0dev.to Go