TL;DR
Get business pricing on networking and server gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
PostgreSQL 19 is likely to arrive in November rather than its customary September-to-mid-October window, according to a PostgreSQL developer writing about the release. The developer links the delay and several late feature reverts to a surge in bugs found with help from large language models, while noting that the project has not announced a final release date.
PostgreSQL 19 is likely to be released in November, later than the project’s usual September-to-mid-October window, as developers face a rise in bug reports that one PostgreSQL contributor attributes largely to large language models (LLMs). The project has also reverted several major features late in the beta period; the contributor says the added repair and review workload helped delay release preparation, but a final release date has not been announced in the source material.
In a report published in October 2026, PostgreSQL developer Robert Haas said the timing of major releases had been fairly predictable over the past decade, with releases generally arriving between mid-September and mid-October. For PostgreSQL 19, he wrote, a November release was more likely, and a further postponement could not be ruled out. The report does not cite an official release-date announcement from the project.
Haas pointed to three sizable features that were removed between August 27 and September 15: UPDATE/DELETE FOR PORTION OF, SQL Property Graph Queries (SQL/PGQ), and ALTER TABLE … MERGE PARTITION/SPLIT PARTITION. He described multiple large reverts at that late point in the beta as unusual, although he noted that features are sometimes removed after the annual feature freeze, which falls on April 8.
His account compares repository commit counts over the same dates in 2025 and 2026. From April 8 to September 25, commits to the current development branch rose from 1,037 to 1,443, while commits to the in-progress stable branch rose from 724 to 1,169. The latter is an increase of more than 60%, according to Haas. On the previous stable branch, counts rose from 248 commits to REL_17_STABLE in 2025 to 433 to REL_18_STABLE in 2026, which he described as a jump of more than 74%. These figures count commits during the stated periods; they do not by themselves establish why the work increased.
How AI Bug Reports Affect Release Work
The episode shows how AI-assisted bug discovery can add work to a mature open-source project even when AI tools also help draft fixes. Haas said reports from people using LLMs have drawn attention to defects across PostgreSQL’s active and older release branches. Each report still needs investigation, and a proposed patch must be checked before maintainers accept it.
That workload competes with the review needed to ship a major release. In Haas’s explanation, developers spent more time addressing bugs and security issues in supported branches, leaving less time to evaluate release candidates and decide which new features were safe to retain. The resulting delay is a trade-off: holding a release for additional review can be preferable to shipping changes that have not been adequately checked. The source does not quantify the delay in days or establish how much of it is attributable to AI-assisted reports.
The broader concern is capacity. LLMs may help uncover defects faster than a volunteer and professional maintainer community can validate and fix them. Haas said the longer-term effect on PostgreSQL’s ability to keep up with maintenance while continuing to add features is uncertain, and described the situation as both a challenge and an opportunity for software developers.
Products Worth Considering
Amazon Kindle Paperwhite Signature Edition (12th Generation, 2024), 32 GB, Metallic Raspberry
Bose QuietComfort Wireless Noise-Cancelling Over-Ear Headphones, Twilight Blue
Apple AirPods Pro (1st Generation) with MagSafe Charging Case
As an affiliate, we earn on qualifying purchases.
From Feature Freeze to Late Reverts
PostgreSQL releases follow a development cycle that includes an annual April 8 feature freeze, after which the focus shifts toward stabilizing the release. Haas wrote that feature reverts immediately after the freeze are not especially uncommon. What stood out in the 2026 cycle, in his account, was that several large changes were removed weeks into the beta period, while maintainers were also handling a heavier volume of fixes.
The database project’s code history spans decades, Haas wrote, and its codebase is large and complex. He argues that LLMs have made it easier for people to identify possible bugs in that code. The tools can also suggest fixes, but Haas cautioned that generated patches are not always correct or consistent with PostgreSQL’s standards, so human review remains necessary.
His explanation is a contributor’s assessment rather than a formal project postmortem. The commit totals offer a year-over-year measure of repository activity, but they do not classify the work by cause or prove that LLMs account for the increase. Haas also acknowledged that some additional commits could reflect more mistakes by developers, while saying he did not believe that was the main explanation.
What the Commit Counts Cannot Show
The source provides no confirmed release date for PostgreSQL 19, and it remains unclear whether the project will settle on November or delay further. It also does not give a final schedule for resolving the late reverts or indicate whether any of the removed features could return in a later release.
The claim that LLM-assisted reports are a major reason for increased maintenance work is Haas’s interpretation of the trend. The reported commit totals do not identify which changes were triggered by AI-assisted findings, distinguish bug fixes from other work, or show how many reports were rejected or confirmed. The source also does not provide a project-wide analysis attributing the release delay among bug fixes, security work, feature review, and other factors.
Release Timing Depends on Review
The immediate next step is further stabilization and review before PostgreSQL 19 can ship. Haas’s report suggests the release timing will depend on whether maintainers can complete that work and decide which changes are ready to include; it does not list a date for a new release milestone. Readers should look to official PostgreSQL project announcements for a confirmed schedule.
Beyond version 19, maintainers will need to work out how to handle the continuing flow of bug reports and proposed fixes without weakening review standards or slowing new development. Haas said he and other contributors are working on that problem, but did not describe a specific policy or tooling change already adopted by the project.
Key Questions
When is PostgreSQL 19 expected to be released?
PostgreSQL developer Robert Haas said a November 2026 release is likely, with a further delay possible. The source does not provide an official release date.
Why does Haas link the delay to AI?
Haas says people are using LLMs to find and report more bugs across PostgreSQL releases. Investigating reports and reviewing proposed fixes take maintainer time, which he says has also been diverted from release review.
Which features were removed late in the beta?
The report names UPDATE/DELETE FOR PORTION OF, SQL Property Graph Queries (SQL/PGQ), and ALTER TABLE … MERGE PARTITION/SPLIT PARTITION. Haas says they were reverted between August 27 and September 15.
Do the commit figures prove AI caused the increase?
No. They show more commits to the in-progress and prior stable branches in the specified 2026 period than in the comparable 2025 period. The figures do not label the cause of each change; the link to LLM-assisted bug discovery is Haas’s assessment.
Does AI write and approve PostgreSQL fixes?
Haas says LLMs can draft fixes, but their suggestions may be incorrect or fail to meet PostgreSQL standards. Human review and approval remain necessary, according to his account.
Source: rhaas.blogspot.com
