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
go-endure: I Wanted Durable Functions Without The Headache — So I Built My Own
0dev.to

Alibaba Cloud Dynatrace: monitor ECS, SLB and databases in multi-cloud
0dev.to
Encontré 2 bugs reales en Django y decidí no reportarlos. La razón es más interesante que el bug.
0dev.to

Research Quest: construindo um RAG confiável e de baixo custo — Parte 1
0dev.to
How to network for an internship as a college student
0dev.to
Show HN: PG Import Check – Analyze PostgreSQL schemas before importing data
0Hacker News Show