PostgreSQL 19 was supposed to ship in October. The release team now says general availability is November 19, with RC 2 on November 12 (postgresql.org’s RC 1 announcement has the dates). The reason is the interesting part.
What happened
According to The Register’s report, developers reverted or pulled between 8 and 10 significant features and pushed them to PostgreSQL 20. Some of them, like SQL/PGQ graph queries, had architectural issues that would have been hard to fix during beta.
LLM-assisted code review also surfaced a long list of defects. The Register cites roughly 40 defect reports, mostly small edge cases that would previously have turned up later, if at all.
It wasn’t “vibe coding”
Peter Eisentraut (EDB, a PostgreSQL committer) was explicit, as relayed by The Register: vibe coding did not cause the reverts, because those tools weren’t available when most of the features were written. The AI didn’t write the bugs. It found them.
One caveat. Independent write-ups argue that AI wasn’t the only cause. Review capacity, and late-cycle review timing, mattered too. Treat “AI found the bugs” as the headline, not the whole story.
The real lesson: the bottleneck moved
Every defect still needs a human to triage it, fix it, test it, and review the fix. Finding bugs got cheap. Fixing them didn’t.
If you maintain a codebase, the practical takeaways are:
I’m biasing toward small, verified commits. I build Vigilante, a free game that turns GitHub-verified commits into a settlement you build. It’s a small nudge toward the habit this story argues for.
Sources: postgresql.org RC 1 announcement; The Register (Oct 16, 2026).