PostgreSQL 13 End of Life (EOL): Ended 13 November 2025, What to Do Now
PostgreSQL 13 reached end of life on 13 November 2025 with its final release, 13.23. Databases keep running, but the PostgreSQL project ships no more fixes, and the big clouds now charge to patch it.
Written Updated Shahzeb Umer
SubscribeStatus
No longer supported
Support ended .
- Since end of life
- 371 days
- Final release
- 13.23
- Move to
- PostgreSQL 18fixed until 14 Nov 2030
5.1 years of support
- Supported24 Sep 2020 – 13 Nov 2025
- No fixes13 Nov 2025 – today
Supported for 5.1 years, from 24 Sep 2020 to 13 Nov 2025.
Who still patches it
Nine places PostgreSQL 13 runs, nine deadlines.
- PostgreSQL (community): Final release 13.23, 13 Nov 2025
- Heroku Postgres: End of life 29 Oct 2024
- Docker image (postgres:13): Last rebuilt 14 Nov 2025
- RHEL 8 (postgresql:13 stream): Stream retired May 2026
- Debian 11 (postgresql-13): Debian LTS ended Aug 2026
- Azure flexible server: Extended support to Nov 2028
- Google Cloud SQL: Extended support to Feb 2029
- Amazon RDS, Aurora: Extended Support to Feb 2029
- RHEL 9 (postgresql, default): Patched to May 2032
Where to move
Be on PostgreSQL 18.
The short version
- PostgreSQL 13 reached end of life on 13 November 2025. Its final release, 13.23, came out that day, and the PostgreSQL project has published no fixes for 13 since, security fixes included, through five update releases for 14 to 18.
- Patching 13 now mostly costs money. Cloud SQL has billed for extended support since 1 February 2026, RDS and Aurora since 1 March 2026 and Azure since 1 September 2026, and all three end it between November 2028 and February 2029. RHEL 9, which ships 13 as its default, patches its own package until May 2032.
- Move to PostgreSQL 18. It is supported until 14 November 2030, runs on RDS, Aurora, Cloud SQL, Azure and Heroku today, and pg_upgrade or logical replication can take a 13 database there in one step.
On this page
PostgreSQL 13 reached end of life on 13 November 2025. That day the PostgreSQL project published its final release, 13.23, and said 13 "will no longer receive security and bug fixes". A year on, your databases still run: nothing in PostgreSQL checks the date, and a server on 13.23 behaves the same now as it did then.
What stopped is the supply of fixes, and the project has fixed dozens of vulnerabilities in later versions since. Whether anyone patches your 13 depends on where it runs. The big clouds do, for a fee. Red Hat does for RHEL 9's own package. A server you built yourself or a postgres:13 container has had nothing since 13.23.
What stopped on 13 November 2025
The PostgreSQL project supports each major version for five years after its first release, then publishes a final minor release and stops. 13.0 came out on 24 September 2020.
13.23 was the last of those minor releases. It shipped on 13 November 2025 alongside 18.1, 17.7, 16.11, 15.15 and 14.20, and that batch fixed 2 security vulnerabilities and over 50 bugs. The announcement is plain: "This is the final release of PostgreSQL 13." The 13.23 release notes add that users "are encouraged to update to a newer release branch soon".
Since then the project has published five update releases for 14 to 18, on 12 and 26 February, 14 May, 13 August and 12 November 2026, and nothing for 13. Its security pages list only supported versions as affected, so they do not tell you whether a new vulnerability reaches 13. The vendors that still patch 13 do: AWS's three Extended Support builds fix 32 CVEs from the February, May and August releases between them. The 12 November release alone fixed 52 security vulnerabilities across 14 to 18.
If you are on an older 13.x, update to 13.23 now. It needs no dump and restore, and it is the last community build, with every fix the project made for 13.
Who still patches PostgreSQL 13
| Where it runs | Patched until | What happens after | Source |
|---|---|---|---|
| PostgreSQL community | 13 November 2025, the final release, 13.23 | No further releases | Versioning policy |
| Heroku Postgres | End of life 29 October 2024 | Access restricted and databases deleted after end of life. Heroku's default is 18 | Heroku |
Docker official image postgres:13 |
Last rebuilt 14 November 2025 | Removed from the official images that day. The tag still pulls, with no further rebuilds | Removal commit, Docker Hub |
RHEL 8, postgresql:13 stream |
Retired May 2026. The last fix, RHSA-2026:28208, came on 23 June 2026 | No updates or errata. Red Hat shipped the August 2026 fixes for RHEL 8's 12, 15 and 16 streams, not 13 | Application Streams, CVE-2026-14662 |
Debian 11, postgresql-13 |
Debian LTS until 31 August 2026. Its last 13 update, 13.23-0+deb11u4 (DLA-4646-1), carried the May 2026 fixes | Freexian sells Debian 11 ELTS until 30 June 2031, but on 17 November its tracker listed the August and November 2026 CVEs in postgresql-13 as open |
Debian 11, DLA-4646-1, Freexian tracker |
| Azure Database for PostgreSQL flexible server | Standard support until 31 July 2026, then free extended support in August | Automatic paid extended support from 1 September 2026 to 12 November 2028: $0.07 per vCore-hour in East US, twice that in year 3 | Version policy, extended support, pricing |
| Google Cloud SQL for PostgreSQL | Standard support until extended support started on 1 February 2026 | Automatic paid extended support until 1 February 2029: $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 2026 | Paid RDS Extended Support from 1 March 2026 to 28 February 2029, for Critical and High CVEs: $0.100 per vCPU-hour in US East (N. Virginia), $0.200 from 1 March 2028. The newest RDS build is 13.23-rds.20260819, released 10 November 2026 | RDS calendar, Aurora calendar, pricing |
RHEL 9, default postgresql (13) |
For the life of RHEL 9: maintenance support ends 31 May 2032. RHSA-2026:69607, on 22 September 2026, shipped the August 2026 fixes as postgresql-13.23-6.el9_8 |
Application Streams get no extended life cycle support | Application Streams, RHEL life cycle, RHSA-2026:69607 |
| Ubuntu | Not applicable: no LTS release ships 13 (20.04 has 12, 22.04 has 14) | Not applicable | Launchpad |
RHEL 9 is the long tail. Of the places above, it is the only one still patching 13 at no extra charge. dnf install postgresql-server on RHEL 9 gives you 13, and Red Hat shipped the February, May and August 2026 security fixes for it, three to six weeks after the community did. AlmaLinux 9 and Rocky Linux 9 carried the rebuilt 13.23-9.el9_9 on 17 November 2026. That covers Red Hat's package only. A server built from source, or from the PostgreSQL project's own packages, follows the community date.
Paid extended support covers less than the community did. AWS patches Critical and High CVEs and critical bugs, Cloud SQL patches "all critical and high severity CVEs", and Azure excludes general bug fixes. Azure's own pages also disagree: its version policy says that when the community retires a version, Azure "stops applying bug or security patches to the database engine", while its extended support page promises security patches and critical bug fixes for 13 until 12 November 2028.
Patched builds lag the community. On 17 November 2026, AWS's newest 13 build (10 November) and Cloud SQL's newest 13 maintenance release (29 October) both predated the 12 November community release, and Red Hat listed no RHEL fix yet for its CVEs.
What changed in the year since
Most of the deadlines for 13 have already passed. The rest arrive between November 2028 and May 2032.
Heroku, first, in October 2024. Heroku supports each major version for three years, not five, so its end of life for Postgres 13 was 29 October 2024, a year before the community's. After end of life it restricts access to databases still on that version and deletes them, followers included.
Docker, the day after the final release. On 14 November 2025 the official image dropped 13, with the commit message "Remove PostgreSQL 13 since it is end of life". postgres:13 still pulls, but it has not been rebuilt since 14 November 2025, operating system packages included.
The bill, from February 2026. Cloud SQL enrolled every 13 instance in paid extended support on 1 February 2026, RDS and Aurora billed enrolled databases from 1 March 2026, and Azure from 1 September 2026, after a free August. 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. On RDS, a 2 vCPU instance in US East (N. Virginia) costs an extra $0.200 an hour, about $144 for a 30-day month, doubling from 1 March 2028. Multi-AZ standbys are charged too. Aurora Serverless v2 is billed per ACU-hour instead: $0.085 in US East (N. Virginia), $0.170 in year 3. Cloud SQL's committed use discounts do not apply to extended support, and its read replicas pay the same rate as standalone instances.
Switching Extended Support off upgrades you. On RDS, disabling enrollment on a database already past its standard support date makes AWS upgrade it automatically to the next supported major version. For 13 that is 14, which itself leaves standard support on 28 February 2027.
Distributions, through 2026. RHEL 8's postgresql:13 stream retired in May 2026. Debian LTS for Debian 11 ended on 31 August 2026, and the same day apt.postgresql.org moved Debian 11 to its archive, with "no further updates".
Extensions, long before. TimescaleDB 2.16.0, released 31 July 2024, says "PostgreSQL 13 is no longer supported in TimescaleDB v2.16", so 2.15.x is the last series for 13. PostGIS 3.7.0, released 30 October 2026, requires PostgreSQL 14 to 19 and removed 12 and 13. pgvector still supports 13 and newer.
Forced upgrades, next. Azure's extended support for 13 ends on 12 November 2028; its extended support page does not say what happens to servers still on 13 after that. Cloud SQL upgrades 13 instances to its default major version during maintenance from 1 February 2029. RDS and Aurora attempt to upgrade databases still on 13 after 28 February 2029, and if that fails, AWS "reserves the right to delete" the database, after preserving its data.
Scanner findings, all along. Tenable's Nessus plugin 63347, PostgreSQL Unsupported Version Detection, is rated Critical and works from the server's self-reported version number. Patched builds keep the 13.23 number, as in RHEL 9's 13.23-6.el9_8 and RDS's 13.23-rds.20260819, so the version alone does not show the later fixes.
How to check what you run
Ask the server. The client's version can differ.
SELECT version();
SHOW server_version;
SHOW server_version_num; -- 130023 means 13.23, the final community release
psql --version # client only
pg_lsclusters # Debian and Ubuntu: every local cluster and its version
rpm -q postgresql-server # RHEL 9: 13.23-6.el9_8 or later has the August 2026 fixes
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
If you pay for Extended Support, AWS makes applying its builds your job. On RDS the newest is 13.23-rds.20260819. On Aurora, only 13.9 and 13.23 are eligible for Extended Support.
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>
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)?:13' --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 the default on Cloud SQL and Heroku, Azure supports it, and it is the official Docker image's latest tag. On RHEL 9, a postgresql:18 stream arrived in 9.8 and is supported until November 2030.
17 is the fallback if an extension you need is not ready for 18. It is supported until 8 November 2029. Skip 14, 15 and 16. 14 ended on 12 November 2026, and 15 and 16 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 13 unpatched, or paying for it, 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 13.23. One exception: on Azure, a server with TimescaleDB can upgrade in place from 13 only to 14, 15 or 16.
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/13/bin --new-bindir=/usr/lib/postgresql/18/bin \
--old-datadir=/srv/pg13 --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. 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 13 main wraps the same steps and keeps the old cluster on another port.
Debian 11 first needs a newer Debian. apt.postgresql.org no longer builds for Debian 11, and its 18 packages for it are frozen at 18.6 in the archive. Debian 12 ships 15 and Debian 13 ships 17, and apt.postgresql.org carries 18 for both.
Replication slots do not survive. pg_upgrade migrates logical replication slots and subscriptions only when the old cluster is 17 or later; on 13 they are "silently ignored". Subscribers and anything that reads changes from a slot have to be set up again after the upgrade.
Logical replication gives the shortest outage, which the documentation puts at several seconds. Set wal_level to logical on 13, copy the schema to an 18 server with pg_dump --schema-only, subscribe it to a publication on 13, 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 13 container and restore into a fresh 18 one. The 18 image keeps its data in /var/lib/postgresql/18/docker, so 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. From 13.12 onwards the sync uses logical replication, so a DDL statement 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. - Aurora has the same two routes. Which major versions you can go to directly depends on your exact minor version, so list them with
aws rds describe-db-engine-versions --engine aurora-postgresql --engine-version <version>. - Cloud SQL upgrades in place with pg_upgrade after an optional precheck, takes a pre-upgrade backup, and is driven by
gcloud sql instances patch <instance> --database-version=POSTGRES_18. Itspassword_encryptionflag defaults toscram-sha-256from 14 onwards. - Azure also runs pg_upgrade in place, can skip versions, and blocks the upgrade if its precheck finds a problem. It blocks some extensions outright: orafce for any upgrade from 13, and pgrouting for an upgrade from 13 to 16 or later. There is no automated way back: you restore to a point before the upgrade on a new server.
Changes most likely to bite between 13 and 18
From the "Migration" sections of the 14, 15, 16, 17 and 18 release notes. Items 1, 4, 5 and 10 come from 14, so they are the ones a 13 database meets that a 14 one already has.
1. Array functions changed signature (14). High, with pg_upgrade. array_append(), array_prepend(), array_cat(), array_position(), array_positions(), array_remove(), array_replace() and width_bucket() now take anycompatiblearray instead of anyarray. User-defined aggregates and operators that reference them must be dropped before the upgrade and recreated after.
2. 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.
3. Data checksums on by default (18). High, with pg_upgrade. pg_upgrade needs matching checksum settings. If SHOW data_checksums; says off on 13, create the 18 cluster with initdb --no-data-checksums.
4. SCRAM passwords by default (14), MD5 deprecated (18). Medium. password_encryption now defaults to scram-sha-256, so passwords set after the upgrade are stored as SCRAM, and a driver that only speaks MD5 cannot log in with them. The old Boolean-like values for the setting, such as on, are no longer accepted. From 18, setting an MD5 password raises a warning, and support goes in a future version.
5. clientcert values in pg_hba.conf (14). Medium. clientcert=1, 0 and no-verify are no longer supported; only verify-ca and verify-full remain. Rewrite those lines before you start 18.
6. 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.
7. 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.
8. Settings and languages removed (14 to 17). Medium. operator_precedence_warning and vacuum_cleanup_index_scale_factor went in 14, vacuum_defer_cleanup_age and promote_trigger_file in 16, and old_snapshot_threshold and db_user_namespace in 17. 15 removed plpython2u and plpythonu, and 17 removed the adminpack extension. Clear them out of postgresql.conf and your databases first.
9. 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.
10. Postfix operators removed (14). Low. The factorial operators ! and !! are gone, and user-defined postfix operators are no longer supported; pg_dump and pg_upgrade warn when they find one. Use factorial().
Smaller ones: EXTRACT() returns numeric instead of float8 (14), and a CREATEROLE role needs ADMIN OPTION on a role to change it or its members (16).
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 the same story a year earlier in its life.
Sources
- Versioning policy, roadmap, final 13 release, 13.23, 13.23 release notes, the November 2026 release and CVE-2026-2004: support policy, release dates, end dates for 14 to 18, which versions the security pages list, the 19 schedule
- Release notes for 14, 15, 16, 17 and 18, pg_upgrade, upgrading, upgrading logical replication clusters and logical replication restrictions: breaking changes and upgrade methods
- AWS: RDS and Aurora calendars, Extended Support updates for 13, Extended Support, charges, enrollment, responsibilities, RDS pricing, Aurora pricing, major upgrades, blue/green replication and blue/green limits
- Google Cloud: versions, extended support, PostgreSQL 13 maintenance changelog, pricing and in-place upgrades
- Azure: version policy, extended support, pricing, retail prices API and major version upgrades
- Heroku version support
- Red Hat: Application Streams, RHEL life cycle, RHSA-2026:69607, RHSA-2026:28208 and CVE-2026-14662; AlmaLinux 9 AppStream: RHEL coverage
- Debian 11, DLA-4646-1, Freexian ELTS and its postgresql-13 tracker, apt.postgresql.org, its Debian 11 archive notice and Launchpad: Debian and Ubuntu coverage
- Docker official images, the 13 removal, Docker Hub and the image documentation: image status and layout
- TimescaleDB 2.16.0, PostGIS 3.7.0 and pgvector: extension support
- Tenable plugin 63347: the unsupported-version finding
Common questions
Is PostgreSQL 13 still supported?
What is the last version of PostgreSQL 13?
Does Amazon RDS still support PostgreSQL 13?
What happens to PostgreSQL 13 on Google Cloud SQL and Azure?
Does Heroku support Postgres 13?
Does RHEL 9 still patch PostgreSQL 13?
Which PostgreSQL version should I upgrade 13 to?
How do I upgrade from PostgreSQL 13?
Is it safe to keep running PostgreSQL 13?
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