TL;DR
Get business pricing on monitors, keyboards and dev 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 usual September-to-October window, according to PostgreSQL developer Robert Haas. Haas attributes the delay and several late feature reversals partly to more bugs being reported with help from large language models, while noting that human review and fixes remain necessary.
PostgreSQL 19 is likely to be released in November, later than the project’s usual mid-September-to-mid-October window, as maintainers handle more reported bugs and review late changes, developer Robert Haas said. Haas links the increased bug reports partly to people using large language models (LLMs) to find defects, but the project has not confirmed that AI is the sole cause of the schedule slip.
Haas points to commit counts as evidence of a heavier maintenance workload. From April 8 to September 25, 2026, the REL_19_STABLE branch received 1,169 commits, compared with 724 commits to the corresponding PostgreSQL 18 stable branch over the same dates in 2025. Haas describes the increase in back-patched commits for the release in development as more than 60%. The master branch, by contrast, received 1,443 commits in that 2026 period, down slightly from 1,037 in the comparable 2025 period, according to his figures.
The report also compares maintenance on earlier releases: the PostgreSQL 18 stable branch received 433 commits in the specified 2026 period, versus 248 commits to the PostgreSQL 17 stable branch in the corresponding 2025 period. Haas says that was an increase of more than 74%. These counts measure commits, not unique bugs, and the source does not give an independent breakdown of how many were found with AI tools.
Several major features were removed from PostgreSQL 19 late in its beta period: UPDATE/DELETE FOR PORTION OF, SQL Property Graph Queries (SQL/PGQ), and ALTER TABLE … MERGE PARTITION/SPLIT PARTITION. Haas says the features were reverted between August 27 and September 15. He describes multiple large reversions at that late stage as unusual, while noting that feature removals shortly after the annual April 8 feature freeze are not uncommon.
More Bug Reports Add Release Work
The delay illustrates a trade-off facing a mature database project: tools that help identify defects may improve software quality, while also increasing the amount of work needed to diagnose, fix, and review them. Haas says LLMs can draft fixes, but those proposals are not always correct or consistent with PostgreSQL’s standards. Human developers still need to review and commit changes.
According to Haas, time spent handling security issues and other bugs in supported older branches also took attention away from reviewing the PostgreSQL 19 release. That could delay decisions about which features should remain in the new version. For users and organizations planning upgrades, the immediate effect is a later expected release; the report does not identify a confirmed shipping date or describe changes to a release support policy.
Products Worth Considering
Samsung 49-Inch Odyssey G93SC QD-OLED Curved Gaming Monitor
LG UltraGear 32GX850A-B 32-inch 4K UHD Glossy OLED Gaming Monitor
Apple Watch SE 3 GPS 40mm Smartwatch
As an affiliate, we earn on qualifying purchases.
The Release Schedule and Late Reverts
Haas says PostgreSQL’s major releases have generally arrived between mid-September and mid-October over the past decade. He expects PostgreSQL 19 to fall outside that pattern, most likely shipping in November, and says a further postponement is possible. The date is an estimate in his report, not a formal release announcement.
The project’s feature freeze occurs on April 8 each year, according to Haas. After that point, the work shifts toward stabilizing the release, though features can still be removed when maintainers judge that necessary. The three PostgreSQL 19 reversions cited in the report happened in late August and September, during beta testing.
Haas’s account appeared on his blog and was also published by Neon. His explanation is based on his assessment of commit activity and reports from people working on PostgreSQL; the supplied material does not include a separate project statement verifying that LLM-assisted bug reports caused the delay.
Cause and Release Date Remain Open
No final PostgreSQL 19 release date is provided, and Haas says an additional postponement remains possible. The report does not include a release-team schedule or a project-wide confirmation of the expected November timing.
The role of LLMs is also an attributed explanation, not a measured finding in the material provided. Haas says he believes more mistakes are being found quickly with LLM help, while acknowledging that committers could also have made more mistakes. The commit totals do not identify the source of each bug report, count distinct defects, or establish how much of the increase came from AI tools rather than other factors.
It is also unclear how the project will manage the longer-term volume of newly identified issues alongside feature development. Haas says he and other developers are working on that problem but offers no specific process changes or timetable.
Maintainers Continue Release Review
PostgreSQL maintainers still need to resolve outstanding defects and complete review before issuing PostgreSQL 19. The report does not specify a next milestone or announce when the project will confirm a release date. The immediate expectation from Haas is a November release, with the possibility of further delay if the project decides more time is needed.
For users following the release, the next concrete information will be an update from the PostgreSQL project on its schedule and release readiness. Until then, the November timing should be treated as an estimate, and the late feature reversions as decisions Haas reports were made during the beta period.
Key Questions
When is PostgreSQL 19 expected to be released?
Developer Robert Haas says it will most likely ship in November 2026, later than the usual mid-September-to-mid-October period. He says further delay is possible; no final date is given in the source report.
Why does Haas link the delay to AI?
Haas says people are increasingly reporting PostgreSQL bugs found with help from LLMs. He argues that fixing and reviewing the additional issues, including bugs in older supported branches, has taken time from PostgreSQL 19 release work. This is his explanation, not an independently quantified cause.
Which features were removed from PostgreSQL 19?
Haas says maintainers reverted UPDATE/DELETE FOR PORTION OF, SQL Property Graph Queries (SQL/PGQ), and ALTER TABLE … MERGE PARTITION/SPLIT PARTITION between August 27 and September 15.
Do the commit numbers prove that AI caused the delay?
No. The figures show higher commit totals on stable branches in the periods Haas compared, but they do not identify which changes came from LLM-assisted reports or how many distinct bugs were involved. Haas presents AI-assisted bug finding as a likely factor in the increased workload.
Source: rhaas.blogspot.com
