PostgreSQL 14 End of Life (EOL): Ended 12 November 2026, What to Do Now
PostgreSQL 14 reached end of life on 12 November 2026 with its final release, 14.25. Databases keep running, but the PostgreSQL project ships no more fixes.
Written Updated Shahzeb Umer
SubscribeStatus
No longer supported
Support ended .
- Since end of life
- 7 days
- Final release
- 14.25
- Move to
- PostgreSQL 18fixed until 14 Nov 2030
5.1 years of support
- Supported30 Sep 2021 – 12 Nov 2026
- No fixes12 Nov 2026 – today
Supported for 5.1 years, from 30 Sep 2021 to 12 Nov 2026.
Who still patches it
Six places PostgreSQL 14 runs, five deadlines.
- PostgreSQL (community): Final release 14.25, 12 Nov 2026
- Amazon RDS, Aurora: Extended Support to Feb 2030
- Google Cloud SQL: Extended support to Feb 2030
- Azure flexible server: Extended support to Nov 2029
- Ubuntu 22.04 (postgresql-14): Ubuntu Pro to May 2032
- Docker image (postgres:14): Rebuilt as 14.25, no end announced
Where to move
Be on PostgreSQL 18.
The short version
- PostgreSQL 14 reached end of life on 12 November 2026. Its final release, 14.25, came out that day, and the PostgreSQL project now publishes no more fixes for 14, security fixes included.
- Managed services patch 14 for a few more months, then bill for it. Amazon RDS and Aurora charge for Extended Support from 1 March 2027, and Cloud SQL and Azure move 14 into paid extended support on 1 February 2027.
- Move to PostgreSQL 18. It is supported until 14 November 2030, runs on RDS, Aurora, Cloud SQL and Azure today, and pg_upgrade or logical replication can take a 14 database there in one step.
On this page
PostgreSQL 14 reached end of life on 12 November 2026. That day the PostgreSQL project published its final release, 14.25, and said 14 "will no longer receive security and bug fixes". Your databases keep running: nothing in PostgreSQL checks the date, and a server on 14.25 behaves the same now as it did the day before.
What stops is the supply of fixes. Whether anyone still patches your 14 depends on where it runs: a managed service or Ubuntu may, while a server you installed yourself or a postgres:14 container gets nothing after 14.25.
What stopped on 12 November 2026
The PostgreSQL project supports each major version for five years after its first release, then publishes a final minor release and stops. 14.0 came out on 30 September 2021.
Within those five years, a minor release arrives at least once every three months, carrying only bug, security and data corruption fixes. Minor releases need no dump and restore, and you can go from any 14.x straight to the latest, which includes every earlier fix.
14.25 was the last of them. It shipped on 12 November 2026 alongside 18.7, 17.12, 16.16 and 15.20, and that batch fixed 52 security vulnerabilities and over 140 bugs across the supported branches. The announcement is plain: "This is the final release of PostgreSQL 14." From here on, fixes for 14 have to come from someone else.
If you are on an older 14.x, update to 14.25 now. It needs no dump and restore, and it is the most-patched PostgreSQL 14 there will ever be.
Who still patches PostgreSQL 14
| Where it runs | Patched until | What happens after | Source |
|---|---|---|---|
| PostgreSQL community | 12 November 2026, the final release, 14.25 | No further releases | Versioning policy |
| Amazon RDS for PostgreSQL and Aurora PostgreSQL | Standard support until 28 February 2027 | Paid RDS Extended Support from 1 March 2027 to 28 February 2030, for Critical and High CVEs: $0.100 per vCPU-hour in US East (N. Virginia), $0.200 from 1 March 2029. Databases not enrolled are upgraded | RDS calendar, Aurora calendar, pricing |
| Google Cloud SQL for PostgreSQL | Standard support until extended support starts on 1 February 2027 | Automatic paid extended support until 1 February 2030: $0.07 per vCPU-hour, $0.14 in year 3 (Iowa, without high availability). Then an automatic upgrade to the default version | Versions, pricing |
| Azure Database for PostgreSQL flexible server | Standard support until 31 January 2027 | Automatic paid extended support from 1 February 2027 to 11 November 2029: $0.07 per vCore-hour in East US, doubled in year 3 | Version policy, extended support |
Ubuntu 22.04 LTS (postgresql-14 in main, at 14.24 on 14 November) |
Standard security maintenance until May 2027 | Ubuntu Pro coverage until May 2032 | Release cycle, package |
| Debian | Not applicable: no release ships 14 (Debian 11 has PostgreSQL 13, 12 has 15, 13 has 17) | Not applicable | Debian packages |
| RHEL 8, 9 and 10 | Not applicable: Red Hat lists no PostgreSQL 14 application stream | Not applicable | Application Streams |
Docker official image postgres:14 |
Rebuilt as 14.25 on 12 November 2026, still listed on 14 November | Not published. Docker removed 13 the day after its final release | official-images, Docker Hub |
Managed extended support covers less than the community did. AWS patches Critical and High CVEs and critical bugs, and Azure excludes general bug fixes.
What breaks first
Nothing failed on 12 November. The consequences arrive on other people's schedules.
The bill, from 1 February or 1 March 2027. RDS enrolls a database in Extended Support by default when it is created through the CLI, the API or CloudFormation, though not from the console. The commands below show which of yours are enrolled. AWS's own example, a 2 vCPU db.r5.large in US East (N. Virginia), costs an extra $0.200 an hour, about $144 for a 30-day month. Multi-AZ standbys and read replicas are charged too, Reserved Instance discounts do not apply, and AWS says to find the charge in Cost Explorer by filtering usage types for ExtendedSupport. Cloud SQL and Azure enroll 14 instances automatically, and Azure says the only way to stop the charge is to upgrade.
Forced upgrades, later. RDS upgrades databases with Extended Support disabled on or shortly after 28 February 2027, and attempts to upgrade the rest after 28 February 2030. Cloud SQL upgrades 14 instances to its default version during maintenance from 1 February 2030.
Extensions dropping 14. TimescaleDB 2.20.0, released 15 May 2025, says "PostgreSQL 14 is no longer supported", so 2.19.x is the last series for 14. PostGIS 3.7.0, released 30 October 2026, supports 14 through 19 and dropped 12 and 13, both already past end of life. pgvector still supports 13 and newer.
Frozen container images. When 13 ended, Docker removed it from the official image the next day, with the commit message "Remove PostgreSQL 13 since it is end of life". postgres:13 still pulls, but has not been rebuilt since 14 November 2025, operating system packages included. On 14 November 2026 postgres:14 was still listed at 14.25; if it goes the same way, it stops getting rebuilds too.
Scanner findings. Tenable's Nessus plugin 63347, PostgreSQL Unsupported Version Detection, is rated Critical and works from the version number, so once your scanner treats 14 as unsupported, no 14.x release clears it.
How to check what you run
Ask the server. The client's version can differ.
SELECT version();
SHOW server_version;
SHOW server_version_num; -- 140025 means 14.25, the final release
psql --version # client only
pg_lsclusters # Debian and Ubuntu: every local cluster and its version
On AWS, list RDS and Aurora PostgreSQL databases with their versions and Extended Support enrollment, once per region:
aws rds describe-db-instances \
--query "DBInstances[?Engine=='postgres'].[DBInstanceIdentifier,EngineVersion,EngineLifecycleSupport]" \
--output table
aws rds describe-db-clusters \
--query "DBClusters[?Engine=='aurora-postgresql'].[DBClusterIdentifier,EngineVersion,EngineLifecycleSupport]" \
--output table
On Google Cloud and Azure:
gcloud sql instances list --format="table(name,databaseVersion)"
az postgres flexible-server list --query "[].{name:name, version:version}" --output table
For containers, check what runs and what your files pin:
docker ps --format '{{.Names}}\t{{.Image}}' | grep -i postgres
docker exec <container> postgres --version
grep -rnE 'postgres(ql)?:14' --include='*.yml' --include='*.yaml' --include='Dockerfile*' .
Which version to move to: 18
Target PostgreSQL 18. It is the newest stable major version, now at 18.7, supported until 14 November 2030. RDS has offered it since 14 November 2025 and Aurora since 11 June 2026, it is Cloud SQL's default, Azure supports it, and it is the official Docker image's latest tag. On Ubuntu 22.04, install it from apt.postgresql.org.
17 is the fallback if an extension you need is not ready for 18. It is supported until 8 November 2029. Skip 15 and 16, which end on 11 November 2027 and 9 November 2028.
PostgreSQL 19 came out on 19 November 2026. RDS commits to new major versions within 30 days of the first minor release and Aurora within 8 months, so waiting for 19 means running 14 unpatched for longer.
Jump straight there. postgresql.org says you can skip intervening major versions, as long as you read their release notes. pg_upgrade accepts clusters back to 9.2, logical replication works across major versions, and RDS lists 18 as a direct upgrade target from 14.
How to upgrade
pg_upgrade converts a cluster in place. Run it with --check and your chosen mode first:
pg_upgrade --check --link \
--old-bindir=/usr/lib/postgresql/14/bin --new-bindir=/usr/lib/postgresql/18/bin \
--old-datadir=/srv/pg14 --new-datadir=/srv/pg18
The default mode copies data files. --link uses hard links and is much faster, but once the new cluster starts, the old one is unsafe to use and rolling back means restoring from backup. Install the extensions' 18 builds first, and let pg_upgrade carry their definitions across. Afterwards run vacuumdb --all --analyze-in-stages --missing-stats-only, then vacuumdb --all --analyze-only. On Debian and Ubuntu, pg_upgradecluster -v 18 -m upgrade 14 main wraps the same steps and keeps the old cluster on another port.
Logical replication gives the shortest outage, which the documentation puts at several seconds. Set wal_level to logical on 14, copy the schema to an 18 server with pg_dump --schema-only, subscribe it to a publication on 14, and switch once it catches up. Schema changes, sequence values and large objects are not replicated, so freeze DDL and set sequences before the switch.
Managed services. RDS offers an in-place upgrade or a blue/green deployment that keeps an 18 copy in sync and switches over, typically in under a minute. The sync uses logical replication, so a DDL or GRANT on the old side puts it into Replication degraded and you start again, and tables without a primary key cannot take UPDATE or DELETE. Upgrade extensions separately. Cloud SQL and Azure run pg_upgrade in place after a precheck, with downtime. On Azure, the way back is a point-in-time restore to a new server.
Changes most likely to bite between 14 and 18
1. No more CREATE on public for everyone (15). High. New clusters and new databases no longer grant PUBLIC the right to create objects in the public schema. Upgrades and restores keep your old permissions, so this hits fresh CI databases and new environments, as permission denied for schema public. Grant CREATE to the application role, or give it its own schema.
2. Data checksums on by default (18). High, with pg_upgrade. pg_upgrade needs matching checksum settings. If SHOW data_checksums; says off on 14, create the 18 cluster with initdb --no-data-checksums.
3. Safe search_path during maintenance (17). Medium. Maintenance commands such as ANALYZE, CREATE INDEX, REFRESH MATERIALIZED VIEW, REINDEX and VACUUM now run the functions behind expression indexes and materialized views with a safe search_path. Functions that reach other schemas without qualifying them fail. Set search_path on those functions.
4. Exclusive backup mode removed (15). Medium. pg_start_backup() and pg_stop_backup() are now pg_backup_start() and pg_backup_stop(), and pg_is_in_backup() is gone. Home-grown backup scripts break.
5. pg_stat_bgwriter slimmed down (17). Medium. Checkpoint columns moved to pg_stat_checkpointer, and buffers_backend went in favour of pg_stat_io. Dashboards and alerts need updating.
6. Narrower CREATEROLE (16). Low. A CREATEROLE role now needs ADMIN OPTION on a role to change it or its members. Check tooling that provisions roles.
7. MD5 passwords deprecated (18). Low. Setting one now raises a warning, and support goes in a future version. Move to SCRAM.
The cheapest test: restore a copy, run pg_upgrade --check, upgrade it, and point your test suite at it.
Sources
- Versioning policy, roadmap, final 14 release, 14.25, August 2026 release and 19 RC 1: support policy, release dates, end dates for 14 to 18, the 19 schedule
- Release notes for 15, 16, 17 and 18, pg_upgrade, upgrading and logical replication restrictions: breaking changes and upgrade methods
- AWS: RDS and Aurora calendars, Extended Support, charges, enrollment, responsibilities, pricing, Cost Explorer, major upgrades and blue/green limits
- Google Cloud: versions, extended support, pricing and in-place upgrades
- Azure: version policy, extended support, pricing, retail prices API and major version upgrades
- Ubuntu release cycle, Ubuntu package, Debian packages, Red Hat Application Streams and apt.postgresql.org: distribution coverage
- Docker official images, the 13 removal and Docker Hub: image status and push dates
- TimescaleDB 2.20.0, PostGIS 3.7.0 and pgvector: extension support
- Tenable plugin 63347: the unsupported-version finding
Common questions
Is PostgreSQL 14 still supported?
What is the last version of PostgreSQL 14?
Does Amazon RDS still support PostgreSQL 14?
Which PostgreSQL version should I upgrade to?
How do I upgrade from PostgreSQL 14?
Is it safe to keep running PostgreSQL 14?
Does Ubuntu 22.04 still patch PostgreSQL 14?
Also on the calendar
End-of-life dates for the rest of your stack.
- Kubernetes end of life3 supportedNext to end: 1.35, 28 Feb 2027
- Microsoft .NET end of life2 supportedNext to end: 11, 14 Nov 2028
- Node.js end of life3 supportedNext to end: 22, 30 Apr 2027
- OpenSSL end of life3 supportedNext to end: 4.0, 14 May 2027
- PHP end of life5 supportedNext to end: 8.2, 31 Dec 2026
- PostgreSQL end of life5 supportedNext to end: 15, 11 Nov 2027
- Python end of life5 supportedNext to end: 3.11, Oct 2027
- Ubuntu end of life4 supportedNext to end: 22.04, 1 Jun 2027
Dates checked against endoflife.date (MIT), and the end-of-life date against postgresql.org. How we check datesReport a wrong dateEvery PostgreSQL version