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 now expected to ship in November, later than the project’s typical mid-September to mid-October window, according to a PostgreSQL developer’s report. The developer attributes the delay and several late feature reversions partly to a rise in bugs reported with the help of large language models, while noting that people still need to review and validate fixes.
PostgreSQL 19 is likely to arrive in November 2026, later than the database project’s usual release window, as developers handle a larger stream of bug reports and late changes, according to PostgreSQL developer Robert Haas. Haas argues that LLM-assisted bug discovery has contributed to the workload, but the project has not announced a final release date in the supplied report.
Haas wrote that PostgreSQL major releases over the past decade have generally arrived between mid-September and mid-October. For PostgreSQL 19, he said a November release was more likely, while a further postponement remained possible. The report presents this as an expectation, not a confirmed schedule from the project.
Three substantial features were reverted late in the beta period: UPDATE/DELETE FOR PORTION OF, SQL Property Graph Queries (SQL/PGQ), and ALTER TABLE … MERGE PARTITION/SPLIT PARTITION. Haas said the reversions occurred between August 27 and September 15, later than is usual for multiple major features to be pulled. He connected the timing to time spent addressing bugs and security issues in maintained release branches, leaving less time for reviewing what should ship in version 19.
Commit counts cited in the report offer a measure of the increased maintenance work. 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%, as Haas calculated. For the prior stable branch, the count rose from 248 commits to REL_17_STABLE during that 2025 window to 433 to REL_18_STABLE in the corresponding 2026 window, an increase of more than 74%. These counts are back-branch commits, not a direct count of bugs or LLM-generated fixes.
More Bug Reports Mean More Release Work
The immediate consequence is a later PostgreSQL 19 release and the removal of features that had been expected to ship. For database users and organizations planning upgrades, the timing matters for testing, deployment schedules, and decisions about whether to adopt the new major version promptly. The report does not say that existing PostgreSQL releases are unsafe or that users need to change their current deployments.
The wider issue Haas describes is a mismatch between the speed of finding defects and the human capacity to verify and repair them. LLMs may help people identify bugs and draft fixes, but Haas says generated fixes still require human review and must meet PostgreSQL’s standards. Meanwhile, developers’ time spent on bugs and security issues in supported branches can compete with reviewing new features. That makes release timing a quality-control question as well as a scheduling one.
Products Worth Considering
Jackery Explorer 2000 v2 Portable Power Station with Two 200W Solar Panels
Bose QuietComfort True Wireless Earbuds with Active Noise Cancellation, Black
Samsung 27 Odyssey OLED G5 (G50SF) QHD Gaming Monitor
As an affiliate, we earn on qualifying purchases.
Late Reversions and Commit Counts
PostgreSQL’s annual schedule includes a feature freeze on April 8, after which the project focuses on stabilizing a release rather than adding major features. Haas said large reversions shortly after feature freeze are not especially unusual, but pulling several substantial changes between late August and mid-September stood out. The three named features were reverted during the beta period, before the planned release.
Haas compared activity across matched periods: April 8 through September 25 in 2025 and the same dates in 2026. He reported that commits to the development branch actually declined slightly year over year, while commits to the release branches increased. His explanation is that more people are reporting defects they found using LLMs, increasing the load on PostgreSQL committers. He also acknowledged that the counts alone cannot establish why every commit was made or prove that AI was the cause of the increase.
Release Date and AI’s Exact Role
No final PostgreSQL 19 release date is provided in the report, and Haas says a delay beyond November is possible. The commit figures document increased activity in stable branches, but they do not count bugs directly, identify which reports came from LLM use, or establish how much AI contributed to the workload. Haas presents that connection as his explanation of the trend, not as a measured causal finding.
The report also does not specify how many reported defects were accepted, how many fixes were drafted by LLMs, or the detailed reasons for reverting each feature. It remains unclear how the project will manage a sustained increase in bug discovery alongside feature development and review.
Stabilization Before Version 19
The next milestone is the project’s decision on when PostgreSQL 19 is ready to ship. The report gives November as the likely timing but does not identify a confirmed date or a specific upcoming announcement. Developers will need to continue reviewing fixes and deciding which changes are safe to include before release.
For users, the practical next step is to follow official PostgreSQL release notices for a firm schedule and for the final set of changes. Haas says he and other contributors are working on how to respond to the increase in bugs found with LLM assistance. The longer-term effect on PostgreSQL’s development pace remains unsettled.
Key Questions
When is PostgreSQL 19 expected to be released?
PostgreSQL developer Robert Haas said a November 2026 release is likely, but he also said a further postponement is possible. The report does not give an official release date.
Why does Haas say PostgreSQL 19 is delayed?
Haas links the delay to more bugs being reported with the help of large language models, alongside time spent fixing bugs and security issues in supported release branches. This is his explanation; the report does not establish a precise causal share for AI.
Which features were reverted?
The report names UPDATE/DELETE FOR PORTION OF, SQL Property Graph Queries (SQL/PGQ), and ALTER TABLE … MERGE PARTITION/SPLIT PARTITION. Haas said they were reverted between August 27 and September 15.
Do the commit numbers show that LLMs caused the increase?
No. The figures show more commits to the stable release branches during comparable periods, but they do not measure bug reports or identify their source. Haas argues that LLM-assisted discovery is a likely explanation for much of the rise.
Does the report say current PostgreSQL users should take action?
No specific action for users is recommended. The reported impact is a later major-version release and the removal of several planned features; users should watch for the project’s official schedule and release information.
Source: rhaas.blogspot.com
