Postgres 14 support ends Nov 12, a week before Postgres 19 ships

PostgreSQL 14 gets its final community release on November 12, 2026, and after that the project ships no more fixes for it. The release meant to replace it is late. On October 10, Jonathan Katz, writing for the release team, told the pgsql-hackers list that PostgreSQL 19 general availability had moved to November 19, a week after the next scheduled update release. A second release candidate is now due on November 12, the same day as 14's last update, because the release team wants the large batch of fixes made to the older supported branches in an RC2 before GA.

That leaves 25 days from today until PostgreSQL 14 is out of community support, and no finished version 19 to move to before it goes. For IT teams that run their own Postgres servers, that points to PostgreSQL 18, supported until November 14, 2030, which Snowflake called "the safe upgrade target today" in September. For teams on a managed cloud database, the community date is only part of the picture, because each provider sets its own deadline and charges for running past it.

Why 19 slipped

PostgreSQL 19 was once due in late September or early October, The Register reported, and between eight and 10 significant features were pulled, SQL/PGQ graph queries among them. Snowflake's list of reverts also includes GROUP BY ALL, partition MERGE and SPLIT, and online data checksums. Snowflake's Elizabeth Garrett Christensen counted 53 reverts in the 19 cycle against about 44 for 18.

Peter Eisentraut, a vice president at EDB and a leading PostgreSQL committer, told The Register that AI code review is part of the reason. With LLM-assisted review, he said, such problems "can get found much faster." Committer Tomas Vondra went through the threads behind 12 of the reverts and put just 4 of them down as "probably AI" or "AI," according to a DEV Community analysis. The reverted features will likely land in PostgreSQL 20.

PostgreSQL 14 deadlines, side by side

On RDS, extended support charges apply to every enrolled instance from the day after standard support ends, and standby instances in Multi-AZ setups are billed too, AWS says.

Azure enrolls servers on unsupported versions automatically, and its FAQ says the only way to stop the charges is to upgrade. Its version policy page also says that once the community retires a version, Azure stops applying bug and security patches to the database engine, cannot create new servers on it, and in rare cases may stop a server exposed to a critical flaw. That page gives December 11, 2026 as the end of standard support, while Microsoft's extended support page gives January 31, 2027.

Cloud SQL charges every instance on an end-of-life version for extended support. When that ends, Google upgrades the instance to the default version, which is now PostgreSQL 18.

None of the AWS, Microsoft or Google pages we read gives a price for PostgreSQL 14 extended support, so check your provider's pricing page before you budget.