PostgreSQL 17 End of Life (EOL): November 2029, and When to Move
PostgreSQL 17 is supported until 8 November 2029, but Heroku and Amazon Linux 2023 end it sooner and the clouds start billing for it in 2030. Red Hat and Ubuntu's LTS releases never shipped it. When to move, and whether to skip 18 for 19.
Written Updated Shahzeb Umer
SubscribeStatus
Supported
Support ends .
- Time left
- 1085 days
- Latest release
- 17.12
- Move to
- PostgreSQL 18fixed until 14 Nov 2030
5.1 years of support
- Supported26 Sep 2024 – 8 Nov 2029
Supported for 5.1 years, from 26 Sep 2024 to 8 Nov 2029.
Who still patches it
Eight places PostgreSQL 17 runs, seven deadlines.
- PostgreSQL (community): Final release 8 Nov 2029
- Heroku Postgres: End of life Q3 2028
- Amazon Linux 2023 (postgresql17): Ends with AL2023, 30 Jun 2029
- Azure flexible server: Standard support to 8 Nov 2029
- Google Cloud SQL: Extended support to Feb 2033
- Amazon RDS, Aurora: Extended Support to Feb 2033
- Debian 13 (postgresql-17, default): Debian LTS to 30 Jun 2030
- Docker image (postgres:17): Still rebuilt, no end announced
Where to move
Be on PostgreSQL 18.
The short version
- PostgreSQL 17 reaches end of life on 8 November 2029, the date of its scheduled final release. Until then it is fully supported: the latest release, 17.12, came out on 12 November 2026, and about twelve more quarterly releases are due.
- Other deadlines come first. Heroku ends Postgres 17 in Q3 2028, and Amazon Linux 2023 stops updating it on 30 June 2029. Cloud SQL bills for it from 1 February 2030, RDS and Aurora from 1 March 2030. Debian 13, which installs 17 by default, has Debian LTS until 30 June 2030.
- When you upgrade, go to 18, supported until 14 November 2030 and offered by RDS, Aurora, Cloud SQL, Azure and Heroku today. If you can wait until your platform offers PostgreSQL 19, released on 19 November 2026, skipping 18 saves an upgrade. From 17, pg_upgrade keeps logical replication slots.
On this page
PostgreSQL 17 reaches end of life on 8 November 2029. That is the scheduled date of its final release on postgresql.org, five years after 17.0 came out on 26 September 2024. Until then 17 is fully supported, with the same bug, security and data corruption fixes as 18, in the same quarterly releases.
Three years is a long runway, but the community date is not the first one you meet. Heroku ends Postgres 17 in the third quarter of 2028, Amazon Linux 2023 stops updating it in June 2029, and the big clouds start billing for it in early 2030. 17 is also the version the enterprise distributions skipped: Red Hat has no PostgreSQL 17 stream, and no Ubuntu LTS release ships it. This page lists the dates, then covers the move to PostgreSQL 18 and whether to wait for 19 instead.
What happens on 8 November 2029
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 twelve more 17.x releases, the last on 8 November 2029.
A minor release needs no dump and restore: stop the server, install the new binaries, start it again. Any 17.x can go straight to the latest, which carries every earlier fix.
The latest is 17.12, released on 12 November 2026 alongside 18.7, 16.16, 15.20 and 14.25, in a batch that fixed 52 security vulnerabilities and over 140 bugs across the supported branches. Installing it is the easy part. Three of its notes ask for more:
- Reindex what the notes name. Several of the fixed bugs could corrupt indexes, and the update does not repair an index that is already damaged. Reindex B-tree indexes on columns declared as
bpcharwithout a length (char(n)is not affected), GiST indexes that use pg_trgm'sgist_trgm_ops, and any GIN index you suspect was hit. - Start a fresh chain of incremental backups. Incremental backup is new in 17, through
pg_basebackup --incremental, and the 17.12 notes say existing incremental backup files "should not be trusted". Take a new full backup after updating and base later incrementals on it. - Rebuild C extensions. A security fix for composite types, CVE-2026-6460, needs C-language extensions 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 17.11 and asks you to install 2.32.1 before going further. As of 17 November 2026, 2.32.1 is not out.
Managed services apply minor releases on their own schedule. On 17 November 2026, RDS, Aurora, Cloud SQL and Azure all listed 17.11 as their newest 17 minor. RDS commits to a new minor version within 7 days of the community release, and Aurora within 3 months.
After 8 November 2029 the supply stops. A vulnerability found after that date gets fixed in 18 and later, and in 17 only where someone else maintains it.
Who still patches PostgreSQL 17
| Where it runs | Until | What happens after | Source |
|---|---|---|---|
| PostgreSQL community | 8 November 2029, the scheduled final release | No further releases | Versioning policy |
| Heroku Postgres | End of life Q3 2028 | Deprecated when Heroku Postgres 20 ships; no new 17 databases after three months, forced upgrades scheduled after five, access restricted and databases deleted after six | Heroku |
Amazon Linux 2023, postgresql17 (17.11 in the current package list) |
30 June 2029, when AL2023 itself ends | No further updates from AWS, four months before the community date | AWS |
| Azure Database for PostgreSQL flexible server | Standard support until 8 November 2029 | Not announced for 17. Azure stops patching the engine of a retired version, and put 11 to 14 into automatic paid extended support | Version policy, extended support |
| Google Cloud SQL for PostgreSQL | Standard support until extended support starts on 1 February 2030 | Automatic paid extended support until 1 February 2033: $0.07 per vCPU-hour, $0.14 in year 3 (Iowa, doubled with high availability). Then an automatic upgrade to the default version | Versions, pricing |
| Amazon RDS for PostgreSQL and Aurora PostgreSQL | Standard support until 28 February 2030 | Paid RDS Extended Support from 1 March 2030 to 28 February 2033, for Critical and High CVEs: $0.100 per vCPU-hour in US East (N. Virginia) at today's rates, $0.200 from 1 March 2032. Databases not enrolled are upgraded | RDS calendar, Aurora calendar, pricing |
Debian 13, postgresql-17 (the default; 17.12-0+deb13u1 in trixie-security) |
30 June 2030, the end of Debian LTS for 13 | No further Debian updates | Debian archive, Debian LTS |
| RHEL 8, 9 and 10 | Not applicable: Red Hat lists no PostgreSQL 17 Application Stream | Not applicable | Application Streams |
| Ubuntu LTS | Not applicable: 24.04 ships 16 and 26.04 ships 18 | Not applicable | Ubuntu archive |
Docker official image postgres:17 |
Rebuilt as 17.12 on 12 November 2026 | Not announced. Docker removed 13 the day after its final release | official-images, Docker Hub |
The enterprise distributions skipped 17. Red Hat's Application Streams go from PostgreSQL 16 to 18 on RHEL 9 and 10, and Ubuntu went from 16 in 24.04 to 18 in 26.04. On those systems 17 comes from the PostgreSQL project's own repositories, apt.postgresql.org and yum.postgresql.org, which build 17.12 for Ubuntu 24.04 and 26.04, Debian 13 and RHEL 9 and 10. Their packages, like a postgres:17 container, stop with the community.
Debian 13 is the long tail. Plain postgresql installs 17 there, and Debian ships each new 17.x as a security update: 17.12-0+deb13u1 is already in trixie-security. Debian LTS takes over Debian 13 on 9 August 2028 and runs to 30 June 2030, past the community date. It has patched past a community end before: Debian 11's postgresql-13 got a security update, DLA-4646-1, in June 2026, seven months after 13's final release.
Amazon Linux 2023 stops first among the distributions. It ships 15, 16, 17 and 18 side by side, and AWS stops updating all of them 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
Old minor versions, already. RDS ended standard support for 17.5 and 17.6 on 31 October 2026, and 17.7 to 17.9 follow in March 2027. Aurora ends 17.4 on 30 November 2026, 17.5 on 31 December 2026 and 17.6 on 30 April 2027, and can upgrade a cluster on an unsupported minor for you. Aurora's long-term support minor for 17, 17.7, stays in standard support until 28 February 2030 and is so far the only 17 minor it lists as eligible for Extended Support. AWS's pricing page adds that you "must be on the latest engine minor" to receive Extended Support.
Heroku, in Q3 2028. Heroku supports each major version for three years, not five. When it releases a new major version it deprecates "the third major version released before it", so 16 goes when Heroku Postgres 19 ships and 17 when Heroku Postgres 20 does. Its version page puts 17's end of life in Q3 2028. Heroku's default has been 18 since 4 August 2026.
Extensions, possibly a year or more early. TimescaleDB dropped PostgreSQL 14 in 2.20.0, about 18 months before 14's end of life, and 15 in 2.29.0, about 15 months before 15's. It supports 16, 17 and 18 today and has not said when 17 goes. Your extensions' release notes are where the real deadline shows up.
Amazon Linux 2023, on 30 June 2029. Four months before the community date, postgresql17 on AL2023 gets its last update.
The bill, from February and March 2030. Cloud SQL enrolls every 17 instance in paid extended support on 1 February 2030. RDS and Aurora bill enrolled databases from 1 March 2030, 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. At today's rates, a 2 vCPU instance in US East (N. Virginia), such as the db.r5.large in AWS's own example, costs an extra $0.200 an hour, about $144 for a 30-day month, and $0.400 an hour from 1 March 2032. Multi-AZ standbys are charged too, and Aurora Serverless v2 pays per ACU-hour: $0.085, then $0.170. Azure lists standard support for 17 until 8 November 2029 and has set no extended support dates.
Forced upgrades, later. RDS upgrades databases with Extended Support disabled on or shortly after 28 February 2030, and upgrades the rest when Extended Support ends on 28 February 2033. Cloud SQL upgrades 17 instances to its default major version during maintenance from 1 February 2033.
How to check what you run
Ask the server, not the client. Check checksums and replication slots too, because both decide how the upgrade to 18 goes.
SELECT version();
SHOW server_version_num; -- 170012 means 17.12
SHOW data_checksums; -- off means the 18 cluster needs initdb --no-data-checksums
SELECT slot_name, slot_type, plugin, active, conflicting FROM pg_replication_slots;
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 17:
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 17
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)?:17' --include='*.yml' --include='*.yaml' --include='Dockerfile*' .
Move to 18 now, or wait for 19?
| 17 | 18 | 19 | |
|---|---|---|---|
| First release | 26 Sep 2024 | 25 Sep 2025 | 19 Nov 2026 |
| Community end of life | 8 Nov 2029 | 14 Nov 2030 | Nov 2031 |
| Latest, 19 Nov 2026 | 17.12 | 18.7 | 19.0 |
| RDS and Aurora standard support | 28 Feb 2030 | 28 Feb 2031 | Not yet offered |
| Heroku end of life | Q3 2028 | Q3 2029 | Not yet offered |
| Default in | Debian 13 | Ubuntu 26.04, Cloud SQL, Heroku, Docker latest |
None yet |
Nothing forces a move before 2028. Unless you run on Heroku or Amazon Linux 2023, 17 is patched at no extra cost until late 2029 wherever it runs. The real question is which version your next upgrade should land on.
Upgrading in the next few months: go to 18. It is the newest major version every platform runs, now at 18.7, and 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, Docker's latest tag points to it, Ubuntu 26.04 installs it as postgresql, and RHEL 9.8 and 10.2 added a PostgreSQL 18 stream supported until November 2030. It buys one year more than 17. The PostgreSQL 18 page covers what changes when you get there.
Upgrading later: skip to 19. PostgreSQL 19 came out on 19 November 2026 and is supported until November 2031, a year past 18, and 17 to 19 is one pg_upgrade, the same as 17 to 18. The catch is the platforms. RDS commits to a new major version within 30 days of its first minor release, 19.1, and the project's next scheduled minor release date is 11 February 2027. Aurora allows itself 8 months from 19.1, and Cloud SQL 90 days from general availability. For 18, RDS arrived on 14 November 2025, the day after 18.1, Cloud SQL made it generally available on 20 November 2025, Aurora followed on 11 June 2026 and Heroku on 4 August 2026. 19's release notes also ask pg_upgrade users with full text search, pg_trgm or fuzzystrmatch indexes to read 19's migration notes, as they may need to reindex.
Skip versions freely. postgresql.org says you can go from one major version to another without the ones in between, as long as you read their release notes. pg_upgrade accepts clusters back to 9.2, and RDS lists 18.6 as a direct upgrade target from 17.11.
How to upgrade 17 to 18
pg_upgrade converts a cluster in place. Install the 18 binaries and your extensions' 18 builds, then run it with --check and your chosen mode:
pg_upgrade --check --link \
--old-bindir=/usr/lib/postgresql/17/bin --new-bindir=/usr/lib/postgresql/18/bin \
--old-datadir=/srv/pg17 --new-datadir=/srv/pg18
The default mode copies the data files. --link uses hard links and --clone uses reflinks where the file system supports them. New in 18, --swap moves the data directories across and can be the fastest of all, but once the transfer starts the old cluster is unsafe to start, and the documentation recommends --sync-method=fsync with it. pg_upgrade 18 carries most optimizer statistics across, though not those made with CREATE STATISTICS, so finish with vacuumdb --all --analyze-in-stages --missing-stats-only, then vacuumdb --all --analyze-only. Use the vacuumdb from 18.7 or later: before 18.7, that first command let a database owner run SQL as the user running it (CVE-2026-116313).
Logical replication slots come along. This is what 17 changed. pg_upgrade migrates logical slots and subscription state only when the old cluster is 17 or later, so a 16 upgrade loses them and a 17 upgrade keeps them. On the publisher, the new cluster needs wal_level = logical, max_replication_slots at least the number of slots, the slots' output plugins installed, and no permanent logical slots of its own; on the old cluster, every slot must have sent all its changes and none may be marked conflicting. Disable subscriptions with ALTER SUBSCRIPTION ... DISABLE before upgrading the publisher, and enable them afterwards. On a subscriber, every table must be in state i or r, and the new cluster's max_active_replication_origins, a setting new in 18, must cover the number of subscriptions.
Managed services handle slots their own way. RDS keeps logical slots through a major upgrade from 17 or later, except slots on read replicas, and fails the upgrade if a slot still holds unconsumed WAL. Cloud SQL's in-place upgrade deletes all logical slots, whatever the version. Azure's upgrade validation checks look at logical slots, so run them before you plan around keeping any.
Debian and Ubuntu. Debian 13's archive has no 18, so add apt.postgresql.org first. Then pg_upgradecluster -v 18 -m upgrade 17 main wraps pg_upgrade, gives the new cluster checksums only if the old one had them, and moves the old cluster to another port with manual startup. Its default method is a dump and restore, which turns checksums on for 18, so pass -m upgrade or -m link for the faster route.
Logical replication instead of pg_upgrade gives the shortest outage, which the documentation puts at several seconds. Copy the schema to an 18 server with pg_dump --schema-only, subscribe it to a publication on 17, 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. The 17 image keeps its data in /var/lib/postgresql/data, with the volume there. The 18 image keeps it in /var/lib/postgresql/18/docker, under a volume at /var/lib/postgresql, and exits with an error when it finds data from the old layout or another version, so changing the tag converts nothing. Either dump from the 17 container and restore into a fresh 18 one, or run pg_upgrade with both versions' binaries. For pg_upgrade, the image maintainers suggest moving 17's files into a 17/docker subdirectory and running 17 with PGDATA=/var/lib/postgresql/17/docker and the volume at /var/lib/postgresql, so pg_upgrade --link later stays within one mount. If 17's checksums are off, also add --no-data-checksums to POSTGRES_INITDB_ARGS for the new cluster.
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 a major upgrade the sync uses logical replication, so a DDL or a
GRANTon the old side puts it into Replication degraded and you start again, large objects are not copied, and tables without a primary key cannot takeUPDATEorDELETE. Upgrade extensions separately. - Cloud SQL upgrades in place with
gcloud sql instances patch <instance> --database-version=POSTGRES_18, after an optional precheck, and takes a pre-upgrade backup to restore from. For 18 it asks you to upgrade PostGIS to 3.6.0 first, and it drops logical slots, as above. - Azure runs pg_upgrade in place after validation checks. There is no automated way back: you restore to a point before the upgrade on a new server. TimescaleDB servers can go from 17 to 18 in place, and
pg_failover_slotsblocks an upgrade to 17 or 18. - Heroku upgrades with its
pg:upgradecommands and--version 18, with around 10 minutes of downtime for most databases. Without--version, it goes to the newest version Heroku offers. - Aurora has the same two routes as RDS. Which major versions you can reach 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 17 and 18
From the "Migration to Version 18" section of the 18.0 release notes, plus two changes elsewhere in them that affect upgrades and monitoring.
1. Data checksums on by default. High, with pg_upgrade. 18's initdb enables checksums, and pg_upgrade needs the old and new clusters to match. 17's initdb did not enable them, so many 17 clusters have them off. If SHOW data_checksums; says off, create the 18 cluster with initdb --no-data-checksums.
2. Keys on nondeterministic collations. Low, but it blocks the upgrade. A primary key and the foreign keys that reference it must now use deterministic collations, or the same nondeterministic one. The notes say a pg_dump restore, which pg_upgrade also uses, fails otherwise, so the schema has to change first.
3. Monitoring columns removed. Medium. pg_stat_wal lost wal_write, wal_sync, wal_write_time and wal_sync_time, and track_wal_io_timing now feeds pg_stat_io instead. pg_stat_io dropped op_bytes for new read_bytes, write_bytes and extend_bytes columns. pg_backend_memory_contexts lost parent, and its level now counts from one. Dashboards and alerts built on these need updating.
4. MD5 passwords deprecated. Low. CREATE ROLE and ALTER ROLE now warn when they set an MD5 password, and support goes in a future major version. md5_password_warnings = off silences the warning; moving to SCRAM removes the cause.
5. VACUUM and ANALYZE reach inheritance children. Low. Run on a parent table, they now process its children too, which can lengthen maintenance jobs. VACUUM ONLY and ANALYZE ONLY keep the old behaviour.
6. Full text search follows the cluster's collation provider. Low. It used to read configuration files and dictionaries with libc. Clusters whose default provider is ICU or builtin can see different results from full text search and pg_trgm, and the notes recommend reindexing those indexes after pg_upgrade.
7. New error code for RESTRICT foreign keys. Low. Violations of a RESTRICT foreign key report SQLSTATE 23001 (restrict_violation) instead of 23503. Code that catches 23503 by number misses them.
8. COPY and CSV end markers. Low. COPY FROM no longer treats \. as end of file in CSV, and \. must stand alone on a line. Older psql clients can have \copy problems against an 18 server.
Smaller ones: AFTER triggers run as the role that was active when the event was queued, not at commit; unlogged partitioned tables are no longer allowed; the session's time zone abbreviations now win over timezone_abbreviations; generated columns are virtual unless you write STORED; and EXPLAIN ANALYZE includes buffer counts by default, which changes output that tools parse.
The cheapest test is a rehearsal: 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. PostgreSQL 16 has the changes 17 itself brought, and PostgreSQL 14 shows what the platforms do once a version's final release is out.
Sources
- Versioning policy, roadmap, the November 2026 release, the 17.12 release notes and CVE-2026-116313: support policy, end dates, the latest 17 release and the 19 schedule
- Release notes for 17 and 18, pg_upgrade, upgrading logical replication clusters, upgrading, logical replication restrictions and pg_upgradecluster: breaking changes and upgrade methods
- AWS: RDS and Aurora calendars, Aurora LTS releases, Extended Support, charges, enrollment, support dates, RDS pricing, Aurora pricing, major upgrades, the upgrade process and logical slots, blue/green overview, replication and limits
- Google Cloud: versions, extended support, pricing, release notes and in-place upgrades
- Azure: version policy, supported versions, extended support and major version upgrades
- Heroku: version support, Postgres 18 general availability and upgrading
- Distributions: Debian archive, Debian LTS, DLA-4646-1, Ubuntu archive, Red Hat Application Streams, Amazon Linux 2023 packages, apt.postgresql.org and yum.postgresql.org
- Docker official images, the 13 removal and the 18 data directory change: image status and layout
- TimescaleDB 2.20.0, 2.29.0 and 2.32.0: extension support
- endoflife.date: PostgreSQL: the dates in the status box, MIT licensed
Common questions
When is PostgreSQL 17 end of life?
Is PostgreSQL 17 still supported?
When does Amazon RDS stop supporting PostgreSQL 17?
How long will Heroku support Postgres 17?
Should I upgrade PostgreSQL 17 to 18 or wait for 19?
Does pg_upgrade keep logical replication slots from PostgreSQL 17?
Which Linux distributions ship PostgreSQL 17?
What is the latest version of PostgreSQL 17?
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