TL;DR
Get the latest gadgets delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
PostgreSQL 19 is likely to arrive in November, later than the project’s usual September-to-October window, according to a report by PostgreSQL developer Robert Haas. Haas links the delay and several late feature reverts to more bugs being found with large language models, while noting that human review and fixes take time.
PostgreSQL 19 is likely to be released in November 2026, later than the database project’s typical mid-September-to-mid-October window, as maintainers handle a larger volume of bug reports and fixes. PostgreSQL developer Robert Haas attributes the increased discovery of defects in part to people using large language models (LLMs), while describing the release delay and late feature removals as consequences of the project’s focus on quality.
Haas wrote that the project could also decide to postpone the release beyond November, so the date is not final. He pointed to three sizable features removed late in the beta period: UPDATE/DELETE FOR PORTION OF, SQL Property Graph Queries (SQL/PGQ), and ALTER TABLE … MERGE PARTITION/SPLIT PARTITION. The reverts occurred between August 27 and September 15. Haas said late reverts can happen after the annual April 8 feature freeze, but removing several major features at that stage is unusual.
Commit counts cited in the report show a marked rise in work on stable branches. From April 8 to September 25, 2026, PostgreSQL recorded 1,169 commits to REL_19_STABLE, compared with 724 to REL_18_STABLE over the same dates in 2025. The corresponding count for the development branch fell slightly, from 1,037 commits in 2025 to 1,443 in 2026? Haas’s comparison says master-branch commits declined slightly; the supplied figures list 1,037 for 2025 and 1,443 for 2026, which do not support that description. The figures or comparison therefore need clarification before drawing a conclusion from them.
Haas also reported 433 commits to REL_18_STABLE during the 2026 period, against 248 to REL_17_STABLE in the comparable 2025 period. He interprets the increases as evidence that more defects are being reported across both the release in development and older supported branches. The counts measure commits, however; they do not by themselves establish how many bugs were found or what share were identified with AI tools.
More Bugs Mean More Review Work
The account describes a shift in the workload facing PostgreSQL maintainers: tools that help users spot possible defects can increase the flow of reports, but they do not remove the need to verify and repair them. Haas says LLMs can draft fixes, yet those patches may be incorrect or fail to meet PostgreSQL’s standards. Human review remains necessary, and that work can compete with release preparation.
Haas says attention that might otherwise have gone to reviewing PostgreSQL 19 changes was diverted to security issues and other bugs in older stable branches. That matters because a database release depends on careful testing and decisions about whether changes are safe to ship. In his view, postponing the release is not particularly concerning in itself; he sees it as a limited delay tied to quality control. The wider concern is whether development teams can keep pace if AI-assisted bug discovery continues to expand.
Products Worth Considering
Apple AirPods Pro 3 Wireless Earbuds with Active Noise Cancellation
Samsung 32-inch Odyssey OLED G8 (G80SH) 4K QD-OLED Gaming Monitor
Bose QuietComfort Wireless Earbuds with Active Noise Cancellation, Dewdrop Mint
As an affiliate, we earn on qualifying purchases.
A Break From the Usual Release Window
Haas says PostgreSQL major releases have followed a fairly predictable schedule over the past decade, arriving no earlier than mid-September and no later than mid-October. PostgreSQL 19 appears set to miss that window. The project’s feature freeze takes place each year on April 8, after which developers generally focus on stabilization rather than adding new work.
Some reverts soon after feature freeze are not unusual, according to Haas. The concern this year, as he describes it, is the number and timing of the large removals during the beta period. His post was originally published on the Neon blog and also appeared on his personal blog. The explanation is the author’s assessment of the causes, supported in part by commit counts; it is not presented as a formal project announcement establishing a release date or a single official cause.
Release Date and AI’s Exact Role
No final PostgreSQL 19 release date is provided in the source; November is described as likely, with a further postponement possible. The project has not, in the supplied material, issued a formal statement confirming that AI-assisted reports are the official or sole reason for the delay.
The commit figures are a measure of repository activity, not a direct count of defects or AI-generated reports. Haas presents LLM-assisted discovery as the likely main explanation for the rise in stable-branch fixes, while allowing that other factors may have contributed. The source’s stated comparison of master-branch commits also conflicts with its listed numbers, which show 1,443 in 2026 versus 1,037 in 2025. That discrepancy should be resolved before using the comparison as evidence of a decline.
Maintainers Continue Stabilization Work
PostgreSQL maintainers are expected to continue reviewing fixes, resolving bugs and security issues, and deciding when the release is ready. The next clear milestone is an official project update on the release schedule; until one is provided, November remains an estimate, not a confirmed launch date. Haas says developers are also working on how to handle the longer-term challenge of increased AI-assisted bug discovery, but gives no timetable or specific process changes.
Key Questions
When is PostgreSQL 19 expected to be released?
Haas says it most likely will not ship until November 2026, with a further delay possible. The source does not give a confirmed release date.
Why does Haas link the delay to AI?
He says more people are using LLMs to find and report bugs, adding work for maintainers across current and older stable branches. He describes this as a likely major factor, not a formally confirmed sole cause.
Which PostgreSQL 19 features were reverted?
The report names UPDATE/DELETE FOR PORTION OF, SQL/PGQ, and ALTER TABLE … MERGE PARTITION/SPLIT PARTITION. Haas says they were reverted between August 27 and September 15.
Do the commit counts prove that AI found more bugs?
No. They show a rise in commits to stable branches in the periods Haas compared, but they do not identify which commits resulted from AI-assisted reports or count the defects themselves.
Does the delay mean PostgreSQL 19 is unsafe?
The source does not say that. Haas presents the delay as time spent addressing bugs and reviewing changes, and says he does not consider the schedule slip particularly concerning.
Source: rhaas.blogspot.com
