
What happened
PostgreSQL 19 RC2 was published on November 12, after beta 4 in late September reverted features including SQL/PGQ, and release is now expected November 19.
Why it matters
The rollbacks show that easier bug discovery is changing what ships in a major database release and when, pointing to more such delays across open-source projects.
WHO IT HITSDatabase administrators and application teams planning upgrades to PostgreSQL 19 will see features like SQL/PGQ slip to a later major release, and they may need to adjust migration plans around the November 19 date.
Summaries like this, every morning.
PostgreSQL has kept a predictable cadence, shipping major versions in September or October from PostgreSQL 14 in 2021 through PostgreSQL 18 in 2025. That rhythm broke this cycle. Beta 1 arrived in June 2026 with the usual September or October target, and beta 2 in July kept the schedule. Beta 3 in August dropped "Group By All" from the release without any mention of timing changes. The real shift came in beta 4 in late September, when a long list of features was reverted or removed, including the headline SQL/PGQ property graph query support, online data checksum toggling, temporal updates and deletes, and partition merge/split commands. The release notes framed the decision around reliability first and a predictable schedule second, and said the removed features could return in a later major release after more community development and review.
Two PostgreSQL committers have offered an explanation for why so many issues surfaced at once. Peter Eisentraut wrote on October 8 that some reverted features had significant architectural defects that would be hard to fix quickly during beta, but that there was also a long tail of smaller edge-case issues. In the past, many of those would have appeared much later and been fixed gradually over the following five years; with LLM-assisted code review, they are found much faster, leaving the team staring at a list of roughly forty defect reports. Robert Haas wrote on October 30 that many people on the internet are now reporting bugs they found using LLMs, keeping committers very busy fixing them.
Taken together, the episode shows AI-assisted review feeding directly into release management. Problems that might once have slipped through until after launch are now caught before the final release, and the community's response has been to pull features rather than rush fixes, with the official release now expected on November 19 after RC2 was published on November 12.
Pick your industry and the AI tools you use, and get news related to your work every day.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.
Robbyant released LingBot-Touch, pre-trained on nearly 5,000 hours of real-world tactile data across magnetic…

On November 12, Google launched Gemini 4 Hydrogen, aimed at everyday coding and multi-step agent tasks, and it…

An RBA analysis by Mike Major found job postings fell across all groups since ChatGPT launched in late 2022, w…

Meituan released the weights for LongCat-2.5, a 1.6-trillion-parameter agent model trained on Chinese hardware…

The candidate, first in both the April and July rounds with 397.5 out of 400 and one wrong answer out of 160 q…

A free Zenn curriculum targets engineers who know basic C# syntax and walks them through building an inventory…
