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, later than the project’s usual mid-September-to-mid-October release window, according to a PostgreSQL developer’s account. The developer links the delay and several late feature reversions to a rise in bugs reported with help from large language models, while noting that the explanation is an assessment rather than a formal project announcement.
PostgreSQL 19 is likely to be released in November 2026, later than the project’s customary mid-September-to-mid-October window, as maintainers handle more bug reports and fixes, according to PostgreSQL developer Robert Haas. Haas attributes much of the increase to people using large language models (LLMs) to find defects, but the project has not, in the supplied material, issued a formal explanation confirming that as the cause of the delay.
Haas reported that several substantial features were removed from the release during the beta period: UPDATE/DELETE FOR PORTION OF, SQL Property Graph Queries (SQL/PGQ), and ALTER TABLE … MERGE PARTITION/SPLIT PARTITION. The reversions took place between August 27 and September 15. He said late reversions are not unheard of after the annual April 8 feature freeze, but multiple major removals so late in the cycle are unusual.
His comparison of commit counts suggests that additional maintenance work is part of the picture. From April 8 through September 25, the PostgreSQL 19 stable branch received 1,169 commits in 2026, compared with 724 on the PostgreSQL 18 stable branch over the equivalent 2025 period. The count for an older stable branch also rose: PostgreSQL 18 had 433 commits in the 2026 period, compared with 248 for PostgreSQL 17 in 2025. These are counts of commits, not a direct measure of bugs, and the comparisons cover different release branches in successive years.
Meanwhile, commits to the development branch over the same periods did not rise: Haas counted 1,443 master-branch commits in 2026, down from 1,037 in 2025? No. The supplied figures say 1,443 in 2026 and 1,037 in 2025, so the count increased. Haas’s stated interpretation is that the master-branch activity did not grow as much as stable-branch backports; he says the number of back-patched commits to the current release branch rose by more than 60%, and commits to the prior release branch rose by more than 74%. He argues the pattern is consistent with more defects being reported and fixed in supported releases.
More Bugs Mean More Release Work
The delay reflects a trade-off between release timing and the time available to review and stabilize software. Haas says LLMs can help identify defects and draft fixes, but generated fixes still need human review and may not meet PostgreSQL’s standards. A larger stream of reports can therefore increase the workload without allowing maintainers to accept fixes automatically.
Haas also says maintainers spent time addressing security issues and other defects in older supported branches, leaving less time to review what should remain in PostgreSQL 19. For users and organizations planning upgrades, the likely November timing means schedules may need adjustment. The report frames the delay as a quality-control decision, not evidence that the release has been abandoned or that a specific defect has made the software unsafe.
Products Worth Considering
LG UltraGear 32GX850A-B 32-inch 4K UHD Glossy OLED Gaming Monitor
Amazon Kindle Scribe (64GB) with Premium Pen, Metallic Jade
Bose QuietComfort Wireless Earbuds with Active Noise Cancellation, Dewdrop Mint
As an affiliate, we earn on qualifying purchases.
PostgreSQL’s Release Cycle and Reversions
Haas says PostgreSQL major releases have generally arrived between mid-September and mid-October over the past decade. The project’s feature freeze occurs on April 8 each year; after that point, work shifts toward testing, bug fixes, and preparing the release rather than adding major features.
Feature removals can happen after the freeze, but Haas describes the cluster of late PostgreSQL 19 reversions as unusual. His account appeared on his blog and was also published by Neon. It presents his explanation of the project’s workload and release timing; the supplied source does not include a separate statement from PostgreSQL’s release team.
Release Date and AI’s Exact Role
November is a forecast, not a confirmed release date in the supplied report. Haas says a further postponement is possible. The commit totals show increased activity on stable branches, but they do not establish how many reports came from LLM use or prove that AI-assisted bug finding caused the delay.
The source also does not give a final list of features that will ship, the number or severity of outstanding defects, or a release-team timetable. The relative contributions of bug discovery, security work, review capacity, and other release tasks have not been quantified.
Maintainers Continue Stabilization Work
The immediate next step is continued testing, review, and bug fixing on the release branch. Maintainers will need to determine which changes are safe to include and whether additional feature removals or schedule changes are warranted. Haas’s account indicates that the release could move beyond November if the project needs more time.
Users waiting to upgrade should watch for an official PostgreSQL release announcement and updated schedule. Until the project publishes one, November remains the developer’s expectation rather than a confirmed launch date.
Key Questions
When is PostgreSQL 19 expected to be released?
PostgreSQL developer Robert Haas says it will most likely arrive in November 2026, but that date is not confirmed and a further delay remains possible.
Why does Haas say the release is late?
He links the delay to more bugs being found and reported with help from LLMs, alongside the time needed to fix and review defects and maintain older release branches.
Which PostgreSQL 19 features were removed?
Haas lists UPDATE/DELETE FOR PORTION OF, SQL Property Graph Queries, and ALTER TABLE partition merge/split operations as features reverted between August 27 and September 15.
Has the PostgreSQL project confirmed AI caused the delay?
Not in the material provided. The AI explanation is Haas’s assessment; the supplied report does not include a formal statement from the PostgreSQL release team confirming the cause.
Source: rhaas.blogspot.com
