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 recent release window, according to PostgreSQL developer Robert Haas. Haas attributes the delay in part to more bugs being found with large language models, which has increased the work of reviewing and fixing defects and contributed to late feature reverts.
PostgreSQL 19 is likely to be released in November, later than the database project’s recent September-to-October window, as developers handle a heavier flow of bug reports and fixes, PostgreSQL developer Robert Haas said. Haas argues that large language models (LLMs) are helping people find more defects in PostgreSQL code, while the human review and repair work has not sped up at the same rate.
Haas reported that three substantial features were 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 took place between August 27 and September 15. While features can be pulled after the annual April 8 feature freeze, Haas said several major reverts so late in the beta period were unusual.
His commit counts point to a rise in fixes to supported release branches. From April 8 to September 25, 2026, PostgreSQL recorded 1,169 commits to REL_19_STABLE, compared with 724 commits to REL_18_STABLE over the equivalent 2025 period — a rise of more than 60%. The master-branch count, by contrast, fell slightly year over year, Haas said. Commits to REL_18_STABLE in the 2026 period reached 433, up from 248 to REL_17_STABLE in the comparable 2025 period, a rise of more than 74%.
Haas links the increase to online bug reports from people using LLMs to inspect the code, while acknowledging that some of the change could reflect more mistakes by committers. He says AI-generated fixes still require human review: suggested patches may be incorrect or fail to meet PostgreSQL’s standards. He also says time spent on security issues and defects in older supported branches reduced the attention available for reviewing changes in version 19.
More Bugs, More Release Work
The delay illustrates a practical tension for a widely used database project: tools that make defects easier to find can also add work before a release is ready. Finding a bug is not the same as validating a fix, especially in mature software where a change can affect other functions or older supported versions.
For users and organizations planning upgrades, the immediate effect is a later and less certain release date. Haas characterizes the delay as limited and as a result of the project’s focus on quality, rather than as evidence that PostgreSQL 19 is unsafe. The late feature removals also mean that some planned capabilities will not ship in this release, though the report does not detail their future schedules.
The broader concern raised by Haas is how maintainers can keep pace if AI-assisted bug discovery continues to expand. More reports may improve software quality, but reviewing, prioritizing and repairing them competes with release work and development of new features.
Products Worth Considering
Amazon Kindle Scribe (64GB) with Premium Pen, Metallic Jade
Samsung 27-inch Odyssey QD-OLED G8 4K 240Hz Gaming Monitor
Amazon Kindle Scribe Colorsoft, 64GB, 11-Inch Color Display with Premium Pen
As an affiliate, we earn on qualifying purchases.
PostgreSQL’s Release Window
Haas says major PostgreSQL releases over roughly the past decade have generally arrived between mid-September and mid-October. PostgreSQL 19 is expected to fall outside that pattern, with November the likely target and a further postponement still possible.
The project’s feature freeze was April 8. After that point, development focuses on stabilizing the release rather than adding major features. Haas notes that reverts shortly after feature freeze are not especially unusual; his concern is the number of large features removed late in the beta period alongside the increased work on bugs across multiple supported branches.
The source for the release outlook and commit comparisons is a report by Haas, originally published on his blog and also published by Neon. Its explanation of why the schedule slipped is his assessment of project activity, not a formal PostgreSQL project statement establishing a single cause.
Release Date and AI’s Role
No final PostgreSQL 19 release date is provided in Haas’s report. November is a forecast, and Haas says the project could delay the release further. The report does not cite a formal project announcement confirming that timetable.
The commit totals show changes over comparable date ranges, but they do not by themselves establish why each fix was made or prove that LLMs caused the increase. Haas presents AI-assisted bug discovery as the likely main explanation, while allowing that other factors, including a higher number of coding mistakes, may have contributed. The report does not quantify how many reports or patches involved LLMs.
It is also unclear how many of the removed features might return in a later PostgreSQL release, or what processes the project may adopt to manage the continuing volume of AI-assisted reports.
Stabilization Before Release
PostgreSQL developers must continue reviewing fixes, addressing issues in supported branches and deciding which changes are safe for version 19. The next key milestone is a project release announcement or updated schedule; until then, November remains Haas’s estimate, not a confirmed ship date.
Haas says developers are working to respond to the wider challenge of AI-driven bug discovery. His report does not describe a specific new policy or timeline for that work. Users planning upgrades should watch for official PostgreSQL project updates on the release schedule and final feature set.
Key Questions
When is PostgreSQL 19 expected to be released?
Robert Haas says the release will most likely come in November 2026, but says a further delay is possible. This is a forecast, not a confirmed release date.
Why does Haas think PostgreSQL 19 is late?
Haas attributes the delay partly to more people using LLMs to find bugs, increasing the amount of work on fixes and review. He also says attention to security issues and bugs in older release branches diverted time from version 19.
Which PostgreSQL 19 features were reverted?
Haas names UPDATE/DELETE FOR PORTION OF, SQL Property Graph Queries (SQL/PGQ), and ALTER TABLE … MERGE PARTITION/SPLIT PARTITION. He says they were reverted between August 27 and September 15.
Do the commit figures prove LLMs caused the delay?
No. The figures show more commits to supported release branches over comparable periods, but they do not identify the cause of each change. Haas presents LLM-assisted bug discovery as the likely main explanation, not as a result established by the counts alone.
Source: rhaas.blogspot.com
