Skip to main content
BumbleTap
Add to ChromeInstall

PostgreSQL 16 End of Life (EOL): November 2028, and What Ends First

PostgreSQL 16 is supported until 9 November 2028, but Heroku, the cloud billing calendars and Linux distributions set their own dates. PostgreSQL 18 is the version to move to.

Written Updated Shahzeb Umer

Subscribe

Status

Supported

Support ends .

Time left
721 days
Latest release
16.16
Move to
PostgreSQL 18fixed until 14 Nov 2030

5.2 years of support

  • Supported14 Sep 2023 – 9 Nov 2028

Supported for 5.2 years, from 14 Sep 2023 to 9 Nov 2028.

Who still patches it

Ten places PostgreSQL 16 runs, nine deadlines.

  • PostgreSQL (community): Final release 9 Nov 2028
  • Heroku Postgres: End of life Q3 2027
  • Amazon Linux 2023 (postgresql16): Patched to 9 Nov 2028
  • Azure flexible server: Standard support to 9 Nov 2028
  • Google Cloud SQL: Extended support to Feb 2032
  • Amazon RDS, Aurora: Extended Support to Feb 2032
  • RHEL 8.10, 9.4+ (postgresql:16 stream): Patched to May 2029
  • Ubuntu 24.04 (postgresql-16, default): Ubuntu Pro to May 2034
  • RHEL 10 (PostgreSQL 16, default): Patched to May 2035
  • Docker image (postgres:16): Still rebuilt, no end announced
Sources: postgresql.org, Heroku Dev Center, Amazon Linux 2023 package list, Azure version policy, Google Cloud SQL versions, AWS RDS and Aurora release calendars, Red Hat Application Streams, Ubuntu release cycle and archive, docker-library official images. Checked 15 Nov 2026.

Where to move

Be on PostgreSQL 18.

The short version

  • PostgreSQL 16 reaches end of life on 9 November 2028, the date of its scheduled final release. Until then it is fully supported: the latest release, 16.16, came out on 12 November 2026, and about eight more quarterly releases are due, the last on 9 November 2028.
  • Other deadlines come first. Heroku ends Postgres 16 in Q3 2027. Cloud SQL bills for it from 1 February 2029, and RDS and Aurora from 1 March 2029. Ubuntu 24.04 (May 2029, or May 2034 with Ubuntu Pro) and RHEL 10 (May 2035) patch their own packages for longer.
  • Move to PostgreSQL 18, supported until 14 November 2030 and available on RDS, Aurora, Cloud SQL, Azure and Heroku today. 17, supported until 8 November 2029, is the fallback. PostgreSQL 19 came out on 19 November 2026, but the managed services don't offer it yet.
On this page
  1. What happens on 9 November 2028
  2. Who still patches PostgreSQL 16
  3. What ends first
  4. How to check what you run
  5. Which version to move to: 18
  6. How to upgrade 16 to 18
  7. Changes most likely to bite between 16 and 18
  8. Sources

PostgreSQL 16 reaches end of life on 9 November 2028. That is the scheduled date of its final release on postgresql.org, five years after 16.0 came out on 14 September 2023. Until then 16 is fully supported: it gets the same bug, security and data corruption fixes as 17 and 18, in the same quarterly releases.

So the community's date is two years away, and it is rarely the one you meet first. Heroku ends Postgres 16 in the third quarter of 2027. The big clouds start billing for it in early 2029. The Linux distributions that ship 16 as their default keep patching it until 2029, 2034 or 2035. This page lists those dates, then covers the move to PostgreSQL 18.

What happens on 9 November 2028

The PostgreSQL project supports each major version for five years after its first release, then publishes a final minor release and stops. Minor releases come at least once every three months, normally on the second Thursday of February, May, August and November. The next is scheduled for 11 February 2027, which leaves about eight more 16.x releases, the last on 9 November 2028.

A minor release needs no dump and restore: stop the server, install the new binaries, start it again. You can go from any 16.x straight to the latest, which carries every earlier fix.

The latest is 16.16, released on 12 November 2026 alongside 18.7, 17.12, 15.20 and 14.25. That batch fixed 52 security vulnerabilities and over 140 bugs across the supported branches, and two of its notes matter when you apply it:

  • Reindex what it names. Some of the fixed bugs could corrupt indexes, and the fixes do not repair existing ones. The 16.16 notes ask you to reindex B-tree indexes on bpchar columns (not char(n)) and GiST indexes that use pg_trgm's gist_trgm_ops, among others.
  • Check your C extensions. A fix for composite types altered while in use needs C-language extensions to be rebuilt for full protection, and the notes warn that some will need source changes. TimescaleDB 2.32.0, released the same day, says it is compatible only up to 16.15 and asks you to upgrade to TimescaleDB 2.32.1 before moving past that. As of 15 November 2026, 2.32.1 is not out.

After 9 November 2028 the supply stops. A vulnerability found after that date gets fixed in 17, 18 and later, and in 16 only where someone else maintains it.

Who still patches PostgreSQL 16

Where it runs Until What happens after Source
PostgreSQL community 9 November 2028, the scheduled final release No further releases Versioning policy
Heroku Postgres End of life Q3 2027 Deprecated when Heroku Postgres 19 ships; no new 16 databases after three months, forced upgrades scheduled after five, access restricted and databases deleted after six Heroku
Amazon Linux 2023, postgresql16 9 November 2028 End of support, no further updates AWS
Azure Database for PostgreSQL flexible server Standard support until 9 November 2028 Not announced for 16. Azure stops patching the engine of a retired version, and gave 11 to 14 automatic paid extended support Version policy, extended support
Google Cloud SQL for PostgreSQL Standard support until extended support starts on 1 February 2029 Automatic paid extended support until 1 February 2032: $0.07 per vCPU-hour, $0.14 in year 3 (Iowa, without high availability). Then an automatic upgrade to the default version Versions, pricing
Amazon RDS for PostgreSQL and Aurora PostgreSQL Standard support until 28 February 2029 Paid RDS Extended Support from 1 March 2029 for Critical and High CVEs, until 29 February 2032 on RDS (28 February 2032 in Aurora's calendar): $0.100 per vCPU-hour in US East (N. Virginia), $0.200 from 1 March 2031. Databases not enrolled are upgraded RDS calendar, Aurora calendar, pricing
RHEL 8.10 and RHEL 9.4 or later, postgresql:16 stream May 2029 The stream retires; no updates or errata Red Hat
Ubuntu 24.04 LTS, postgresql-16 in main (the default; at 16.15 on 15 November) Standard security maintenance until May 2029 Ubuntu Pro coverage until May 2034 Release cycle, package
RHEL 10, PostgreSQL 16 (the default stream since 10.0) For the life of RHEL 10: maintenance support ends 31 May 2035 Application Streams get no extended life cycle support Red Hat
Debian Not applicable: no release ships 16 (Debian 12 has 15, 13 has 17) Not applicable Debian packages
Docker official image postgres:16 Rebuilt as 16.16, last pushed 15 November 2026 Not announced. Docker removed 13 the day after its final release official-images, Docker Hub

The distributions are the long tail. Ubuntu 24.04 and RHEL 10 both install 16 when you ask for plain postgresql, and both commit to patching their own package well past the community's date: Ubuntu 24.04 until May 2029, or May 2034 with Ubuntu Pro, and RHEL 10 for the life of the release. That covers their package only. A server built from apt.postgresql.org, the PostgreSQL project's own repository, or a postgres:16 container follows the community date. Amazon Linux 2023 ships 15, 16, 17 and 18 side by side and ends each with the community, except that all of them stop when AL2023 itself ends on 30 June 2029.

Paid extended support covers less than the community does. AWS patches Critical and High CVEs, and Azure's extended support excludes general bug fixes.

What ends first

Heroku, in Q3 2027. Heroku supports each major version for three years, not five. Its version page lists Postgres 16's end of life as Q3 2027 and spells out the trigger: "Heroku Postgres 16 deprecates when Heroku Postgres 19 releases." PostgreSQL 19 came out on 19 November 2026, and Heroku hasn't said when it will offer it. Three months after the deprecation date Heroku stops new 16 databases, after five it schedules forced upgrades, and after six it starts restricting access and deleting databases still on 16, followers included. Heroku's default is already 18.

Old minor versions, already. Managed services retire 16.x minor versions long before 16 itself. RDS ended standard support for 16.9 and 16.10 on 31 October 2026. Aurora ends 16.9 on 31 December 2026 and 16.10 on 30 April 2027, while its long-term support minor, 16.8, stays in standard support until 28 February 2029. Extended Support has a minor-version catch too: AWS's pricing page says you "must be on the latest engine minor", and Aurora's calendar lists 16.8 as the only eligible 16 minor so far.

Extensions, a year or more early. TimescaleDB dropped PostgreSQL 14 in 2.20.0, on 15 May 2025, about 18 months before 14's end of life, and 15 in 2.29.0, on 28 July 2026, about 15 months before 15's. Its current release supports 16, 17 and 18, and it has not said when 16 goes. If you depend on an extension, its release notes are where the real deadline appears.

The bill, from February and March 2029. Cloud SQL enrolls every 16 instance in paid extended support on 1 February 2029. RDS and Aurora bill enrolled databases from 1 March 2029, and RDS enrolls a database by default when it is created through the AWS CLI or the API, which covers CloudFormation, though not from the console. 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, rising to $0.400 an hour from 1 March 2031. Multi-AZ standbys are charged too. Azure has not set extended support dates for 16; for 14 it enrolls servers automatically and 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 2029, and attempts to upgrade the rest once Extended Support ends. Cloud SQL upgrades 16 instances to its default major version during maintenance from 1 February 2032.

A Docker tag change is not an upgrade. Changing postgres:16 to postgres:18 in a compose file does not convert the data. The 18 image keeps its data in /var/lib/postgresql/18/docker, under a volume at /var/lib/postgresql, and refuses to start when it finds an older data directory. Its error message says this usually comes from upgrading the Docker image without running pg_upgrade, which needs both versions.

How to check what you run

Ask the server. The client's version can differ.

SELECT version();
SHOW server_version;
SHOW server_version_num;  -- 160016 means 16.16
psql --version                 # client only
pg_lsclusters                  # Debian and Ubuntu: every local cluster and its version
rpm -qa 'postgresql*server*'   # RHEL and Amazon Linux: the installed server package

On AWS, list RDS and Aurora PostgreSQL databases with their versions and Extended Support enrollment, once per region, then ask for the support dates of 16:

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

aws rds describe-db-major-engine-versions --engine postgres --major-engine-version 16

On Google Cloud, Azure and Heroku:

gcloud sql instances list --format="table(name,databaseVersion)"
az postgres flexible-server list --query "[].{name:name, version:version}" --output table
heroku pg:info --app <app>     # data:pg:info for Advanced-tier databases

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)?:16' --include='*.yml' --include='*.yaml' --include='Dockerfile*' .

Which version to move to: 18

16 17 18
First release 14 Sep 2023 26 Sep 2024 25 Sep 2025
Community end of life 9 Nov 2028 8 Nov 2029 14 Nov 2030
Latest, 15 Nov 2026 16.16 17.12 18.7
RDS and Aurora standard support 28 Feb 2029 28 Feb 2030 28 Feb 2031
Heroku end of life Q3 2027 Q3 2028 Q3 2029
Default in Ubuntu 24.04, RHEL 10 Debian 13 Ubuntu 26.04, Cloud SQL, Heroku, Docker latest

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 the default on Cloud SQL and Heroku, Azure supports it, and it is the official Docker image's latest tag. RHEL 9.8 and 10.2 added a PostgreSQL 18 stream supported until November 2030, Ubuntu 26.04 ships it as postgresql, and on Ubuntu 24.04 apt.postgresql.org has 18.7.

17 is the fallback if an extension or a tool you need is not ready for 18. It is supported until 8 November 2029, one year more than 16, and is Debian 13's default.

PostgreSQL 19 came out on 19 November 2026. RDS commits to new major versions within 30 days of the community's first minor release, 19.1, Aurora within 8 months and Cloud SQL within 90 days of general availability. With two years left on 16 you have time to wait for it, but 18 is the version every platform above runs today.

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.6 as a direct upgrade target from 16.15.

How to upgrade 16 to 18

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/16/bin --new-bindir=/usr/lib/postgresql/18/bin \
  --old-datadir=/srv/pg16 --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. 18 adds --swap, which swaps directories instead and can also modify the old cluster. Install the extensions' 18 builds before you start. pg_upgrade 18 carries most optimizer statistics across, though not those created with CREATE STATISTICS, so 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 16 main wraps the same steps. It sets up checksums on the new cluster only if the old one used them, moves the old cluster to another port and sets it to start only by hand. Its default method is a dump and restore, so pass -m upgrade or -m link.

Replication slots do not survive. pg_upgrade migrates logical replication slots and subscriptions only when the old cluster is 17 or later. Coming from 16, subscribers and anything that reads changes from a slot have to be set up again after the upgrade. Once you are on 18, later major upgrades keep them.

Logical replication gives the shortest outage, which the documentation puts at several seconds. Set wal_level to logical on 16, copy the schema to an 18 server with pg_dump --schema-only, subscribe it to a publication on 16, 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.

Docker. Each image contains one major version, so pg_upgrade needs a setup with both versions' binaries, or you dump from the 16 container and restore into a fresh 18 one. For 18, mount the volume at /var/lib/postgresql, not /var/lib/postgresql/data.

Managed services.

  • RDS offers an in-place major version upgrade, or a blue/green deployment that keeps an 18 copy in sync and switches over, typically in under a minute. For major versions the sync uses logical replication, so a DDL or a GRANT on the old side puts it into Replication degraded and you start again, large objects are not copied, and tables without a primary key cannot take UPDATE or DELETE. Extensions are upgraded separately.
  • Cloud SQL upgrades in place with pg_upgrade after an optional precheck, takes a pre-upgrade backup to roll back to, and is driven by gcloud sql instances patch <instance> --database-version=POSTGRES_18.
  • Azure also runs pg_upgrade in place, can skip versions, and blocks the upgrade if its precheck finds a problem. There is no automated way back: you restore to a point before the upgrade on a new server. Extensions such as pgvector and TimescaleDB need updating by hand.
  • Heroku upgrades with its pg:upgrade commands, with around 10 minutes of downtime for most databases, or through a follower (20 to 30 minutes) or a data copy (about 3 minutes per GB, for databases under 10 GB).
  • Aurora has the same two routes as RDS. Which major versions you can go to directly depends on your exact minor version, so list them:
aws rds describe-db-engine-versions --engine aurora-postgresql --engine-version <version> \
  --query 'DBEngineVersions[].ValidUpgradeTarget[?IsMajorVersionUpgrade == `true`].EngineVersion' \
  --output text

Changes most likely to bite between 16 and 18

From the "Migration" sections of the 17 and 18 release notes, plus one 18 change that blocks upgrades.

1. Data checksums on by default (18). High, with pg_upgrade. pg_upgrade needs matching checksum settings. If SHOW data_checksums; says off on 16, create the 18 cluster with initdb --no-data-checksums.

2. Safe search_path during maintenance (17). Medium. Maintenance commands such as ANALYZE, CLUSTER, 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.

3. Monitoring views changed (17). Medium. pg_stat_bgwriter lost buffers_backend and buffers_backend_fsync in favour of pg_stat_io, and checkpoint counters moved to the new pg_stat_checkpointer. pg_stat_statements renamed blk_read_time and blk_write_time to shared_blk_read_time and shared_blk_write_time, and pg_stat_progress_vacuum and pg_stat_slru renamed columns. Dashboards and alerts need updating.

4. Settings and an extension removed (17). Medium. old_snapshot_threshold, db_user_namespace and trace_recovery_messages are gone, so a postgresql.conf that still sets one stops the new server from starting. The adminpack extension, used by pgAdmin III, was removed too; drop it before upgrading.

5. Keys on nondeterministic collations (18). Low, but it blocks the upgrade. A foreign key and the key it references must now use deterministic collations, or the same nondeterministic one. The 18 notes say a pg_dump restore, which pg_upgrade also uses, fails otherwise, so the schema has to change first.

6. VACUUM and ANALYZE reach inheritance children (18). Low. Running them on a parent table now processes its children as well, which can lengthen maintenance jobs. VACUUM ONLY and ANALYZE ONLY keep the old behaviour.

7. New error code for RESTRICT foreign keys (18). Low. Violations of a RESTRICT foreign key now report SQLSTATE 23001 (restrict_violation) instead of 23503. Code that catches 23503 by number misses them.

8. MD5 passwords deprecated (18). Low. Setting one now raises a warning, and support goes in a future major version. Move to SCRAM.

Smaller ones: COPY FROM no longer treats \. as end of file in CSV, so older psql clients can have \copy problems against 18; AFTER triggers run as the role that was active when the event was queued; unlogged partitioned tables are no longer allowed; and clusters whose default collation provider is ICU or builtin should reindex full-text search and pg_trgm indexes after pg_upgrade.

The cheapest test: restore a copy, run pg_upgrade --check, upgrade it, and point your test suite at it. Every PostgreSQL version and its dates are on the PostgreSQL hub, and PostgreSQL 14 shows what the platforms do once a version's final release is out.

Sources

Common questions

When is PostgreSQL 16 end of life?
On 9 November 2028. The PostgreSQL project supports each major version for five years after its first release, and 16.0 came out on 14 September 2023. Its final minor release is scheduled for 9 November 2028, after which the project publishes no more 16.x fixes, security fixes included.
Is PostgreSQL 16 still supported?
Yes, fully, until 9 November 2028. It gets the same bug, security and data corruption fixes as 17 and 18, in the same quarterly releases. The latest is 16.16, released on 12 November 2026. Some platforms end it sooner: Heroku's end of life for Postgres 16 is Q3 2027.
When does Amazon RDS stop supporting PostgreSQL 16?
RDS for PostgreSQL keeps 16 in standard support until 28 February 2029. From 1 March 2029, databases enrolled in RDS Extended Support are billed per vCPU-hour: $0.100 in US East (N. Virginia), then $0.200 from 1 March 2031. Extended Support for 16 ends on 29 February 2032, and databases not enrolled are upgraded on or shortly after 28 February 2029.
When does Aurora PostgreSQL 16 reach end of life?
Aurora PostgreSQL 16 is in standard support until 28 February 2029, with paid RDS Extended Support from 1 March 2029 to 28 February 2032: $0.100 per vCPU-hour in US East (N. Virginia), then $0.200 from 1 March 2031. Minor versions end sooner: Aurora 16.9 leaves standard support on 31 December 2026. Its long-term support minor, 16.8, runs to 28 February 2029 and is so far the only 16 minor listed as eligible for Extended Support.
Which PostgreSQL versions are end of life?
As of 15 November 2026, 14 and everything older. 14 had its final release, 14.25, on 12 November 2026, and 13 ended on 13 November 2025. 15, 16, 17 and 18 are supported until 11 November 2027, 9 November 2028, 8 November 2029 and 14 November 2030.
When do PostgreSQL 17 and 18 reach end of life?
PostgreSQL 17 on 8 November 2029 and PostgreSQL 18 on 14 November 2030. On Amazon RDS, standard support runs a little longer, to 28 February 2030 for 17 and 28 February 2031 for 18, followed by paid Extended Support until 28 February 2033 and 28 February 2034.
Which version should I upgrade PostgreSQL 16 to?
PostgreSQL 18. It is supported until 14 November 2030, runs on RDS, Aurora, Cloud SQL, Azure and Heroku, and pg_upgrade or logical replication take a 16 database there in one step. 17 is the fallback if an extension is not ready for 18. PostgreSQL 19 came out on 19 November 2026, but managed services add new major versions weeks or months later.
How long will Heroku support Postgres 16?
Heroku lists Postgres 16's end of life as Q3 2027, more than a year before the community date. Heroku supports each major version for three years and deprecates 16 when it releases Heroku Postgres 19. Three months after deprecation it stops new 16 databases, after five it schedules forced upgrades, and after six it restricts access and deletes databases still on 16.

Also on the calendar

End-of-life dates for the rest of your stack.

Dates checked against endoflife.date (MIT), and the end-of-life date against postgresql.org. How we check datesReport a wrong dateEvery PostgreSQL version