AIThis post was created with the assistance of artificial intelligence (AI).

TL;DR

Buying for a business?Offer from Amazon

Get business pricing on monitors, keyboards and dev gear

  • Business-only prices and quantity discounts
  • Tax-exempt purchasing
  • Multiple users, one account, clear invoices
As an affiliate, we earn on qualifying purchases.

PostgreSQL 19 is now expected to arrive in November, later than the project’s recent release window, according to a PostgreSQL developer’s account. The developer links the delay and several late feature reversions to a sharp rise in bug reports found with large language models, while noting that the explanation is an assessment rather than a formal project finding.

PostgreSQL 19 is likely to be released in November, later than the project’s usual mid-September-to-mid-October window, according to PostgreSQL developer Robert Haas. Haas attributes the delay and several late removals of planned features partly to more bugs being identified with help from large language models (LLMs), which have increased the work needed from human reviewers and maintainers.

Haas’s account, published on his blog and originally appearing on Neon’s blog, says the project may even decide to postpone PostgreSQL 19 beyond November. He points to three sizeable features reverted late in the beta period: UPDATE/DELETE FOR PORTION OF, SQL Property Graph Queries (SQL/PGQ), and ALTER TABLE … MERGE PARTITION/SPLIT PARTITION. The removals occurred between August 27 and September 15. Haas says large reverts can happen after feature freeze, but several being pulled so late is unusual.

He compares repository commit counts across the same dates in two years. From April 8 to September 25, 2025, the master branch received 1,037 commits, while REL_18_STABLE received 724. Over the corresponding period in 2026, master received 1,443 commits and REL_19_STABLE received 1,169. Haas says master-branch activity actually declined slightly after accounting for the comparison, while commits backported to the release branch rose by more than 60%.

The increase was not limited to the version being prepared for release. Haas reports that commits to REL_17_STABLE over the comparable 2025 period numbered 248, versus 433 to REL_18_STABLE in 2026 — a rise of more than 74%. He says people have been reporting bugs found with LLM assistance across PostgreSQL versions, leaving committers busy with fixes. These counts describe commits, not a direct count of bugs, and do not by themselves establish what caused each change.

At a glance
reportWhen: PostgreSQL 19 is expected in November 2…
The developmentA PostgreSQL developer says increased bug reports assisted by LLMs have added review and repair work, likely delaying PostgreSQL 19 until November.

More Reports Mean More Review Work

The delay illustrates a practical cost of AI-assisted software analysis: finding potential defects can outpace the human capacity to verify and repair them. Haas says LLMs can draft fixes, but those patches are not always correct or consistent with PostgreSQL’s standards, so maintainers still need to review them. The added work can compete with release preparation, including decisions about whether new features are ready to ship.

That trade-off matters to users because a later release can mean waiting longer for the new version, but shipping after more review may reduce the risk of releasing defects. Haas characterizes the schedule slip as limited and as a consequence of prioritizing quality. The commit figures show heavier maintenance activity; they do not establish that every additional change was prompted by AI or that more commits automatically mean better software.

Products Worth Considering

Amazon Kindle Paperwhite (2024, 12th Generation), 16 GB, 7-Inch Display, Black

Amazon Kindle Paperwhite (2024, 12th Generation), 16 GB, 7-Inch Display, Black

Logitech MX Mechanical Wireless Illuminated Full-Size Keyboard, Clicky

Logitech MX Mechanical Wireless Illuminated Full-Size Keyboard, Clicky

As an affiliate, we earn on qualifying purchases.

A Break From the Recent Schedule

Haas writes that PostgreSQL major releases over the past decade have generally arrived between mid-September and mid-October. PostgreSQL 19’s likely November timing would fall outside that pattern. Its feature freeze took place on April 8, and the late-beta reversions followed in late summer and early autumn.

Major changes can be removed after feature freeze, Haas says, but he describes multiple large removals this late in the process as unusual. He connects that pattern to two pressures: more defects requiring attention and time taken away from release review to handle bugs and security issues in supported older branches. His explanation is based on his experience and the project’s commit activity, rather than a formal release-team statement quoted in the source.

Release Date and Causes Remain Open

No final PostgreSQL 19 release date is given in the source, and Haas says a further postponement is possible. The project has not, in the material provided, formally confirmed that LLM-assisted bug finding is the cause of the delay. Haas presents it as the likely explanation, while acknowledging that a rise in mistakes by committers could account for some of the increased backport activity.

The commit totals also do not identify which changes came from LLM-assisted reports, distinguish bug fixes from all other commits, or show how much review time each change required. The source offers no independent measurement of LLM use among bug reporters. It remains uncertain whether the higher volume is a temporary surge or a lasting change to PostgreSQL maintenance and release schedules.

Maintainers Continue Review and Fixes

PostgreSQL maintainers still need to review outstanding fixes, address bugs and security issues in supported branches, and decide which changes are safe for the upcoming release. The release could proceed in November, but Haas says the project may push it further if needed. The next clear milestone is an official release schedule or announcement from the PostgreSQL project; none is specified in the source material.

Haas says developers are working on how to respond to the wider volume of defects that LLM-assisted reports may surface. For PostgreSQL 19 users, the immediate practical point is that the timetable remains provisional. The longer-term question is how maintainers can balance fixing newly found problems with reviewing and delivering future features.

Key Questions

When is PostgreSQL 19 expected to be released?

Developer Robert Haas says it will most likely arrive in November 2026, but the date is not final and a further delay is possible.

Haas says people are using LLMs to find and report more bugs in PostgreSQL. Maintainers then have to verify reports, review fixes, and address issues in current and older branches, taking time away from release work.

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 the reverts happened between August 27 and September 15.

Do the commit counts prove that LLMs caused the delay?

No. The counts show more commits to release branches in the compared periods, but they do not identify the cause of each commit. Haas describes LLM-assisted bug reports as the likely explanation, not a formally established finding.

Source: rhaas.blogspot.com

You May Also Like

TorchNeuron On AWS Trainium: Getting Started With System-Level Profiling

Hugging Face’s TorchNeuron tutorial shows how to trace RMSNorm inference across PyTorch, the Neuron runtime and AWS Trainium hardware.

How Our Team Is Getting Ready To Strengthen OpenAI Security

OpenAI says it is preparing a security sprint to harden the company, but its scope, schedule and expected results have not been disclosed.

Three Claude Code Team Members’ Departures Put Anthropic In The Spotlight

Analytics India Magazine reports that three people associated with Claude Code left Anthropic within 10 days, but their identities and reasons are unknown.

An AI Guide To The Benefits Decisions That Come With Resigning

IdeaNavigator AI proposes an assistant to compare resignation dates against benefits documents. The concept has not been validated with users.