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
Implementing Table Partitioning in PostgreSQL
0HackerNoon
Running an Embedding Model Next to My Notes on an iPhone
0HackerNoon
How to increase GMV Max budget without counting orders that have not matured
0dev.to

Do you need bronze, silver and gold layers? Keep three things instead
0dev.to

From Zero to a Running API in Minutes
0dev.to
Laravel Scout and Meilisearch: fast search that keeps working when the engine is down
0dev.to