Skip to main content
BumbleTap
Add to ChromeInstall

PostgreSQL 15 End of Life (EOL): 11 November 2027, and What Ends First

PostgreSQL 15 is supported until 11 November 2027, but Heroku ends it on 28 February 2027 and the clouds start billing for it in early 2028. Who patches 15 until when, and why to move to 18 rather than 16.

Written Updated Shahzeb Umer

Subscribe

Status

Supported

Support ends .

Time left
357 days
Latest release
15.20
Move to
PostgreSQL 18fixed until 14 Nov 2030

5.1 years of support

  • Supported13 Oct 2022 – 11 Nov 2027

Supported for 5.1 years, from 13 Oct 2022 to 11 Nov 2027.

Who still patches it

Ten places PostgreSQL 15 runs, nine deadlines.

  • PostgreSQL (community): Final release 11 Nov 2027
  • Heroku Postgres: End of life 28 Feb 2027
  • Amazon Linux 2023 (postgresql15): Patched to 11 Nov 2027
  • Azure flexible server: Standard support to 11 Nov 2027
  • Google Cloud SQL: Extended support to Feb 2031
  • Amazon RDS, Aurora: Extended Support to Feb 2031
  • RHEL 8 (postgresql:15 stream): Patched to May 2028
  • Debian 12 (postgresql-15, default): Debian LTS to 30 Jun 2028
  • RHEL 9 (postgresql:15 stream): Patched to Nov 2028
  • Docker image (postgres:15): 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, Debian release information and security tracker, docker-library official images. Checked 17 Nov 2026.

Where to move

Be on PostgreSQL 18.

The short version

  • PostgreSQL 15 reaches end of life on 11 November 2027, the date of its scheduled final release. Until then it is fully supported: the latest release, 15.20, came out on 12 November 2026, and four more quarterly releases are scheduled, the last on 11 November 2027.
  • Heroku ends it first: no new Postgres 15 databases since 11 November 2026, forced upgrades from 28 January 2027 and end of life on 28 February 2027. Cloud SQL bills for 15 from 1 February 2028, RDS and Aurora from 1 March 2028. Debian 12, RHEL 8 and RHEL 9 patch their own packages until May to November 2028.
  • Move to PostgreSQL 18, supported until 14 November 2030 and available on RDS, Aurora, Cloud SQL, Azure and Heroku today. Skip 16, which Heroku ends in Q3 2027 and the community a year after 15. 17, supported until 8 November 2029, is the fallback.
On this page
  1. What happens on 11 November 2027
  2. Who still patches PostgreSQL 15
  3. What ends first
  4. How to check what you run
  5. Which version to move to: 18
  6. How to upgrade 15 to 18
  7. Changes most likely to bite between 15 and 18
  8. Sources

PostgreSQL 15 reaches end of life on 11 November 2027. That is the scheduled date of its final release on postgresql.org, five years after 15.0 came out on 13 October 2022. Until then 15 is fully supported, with the same bug, security and data corruption fixes as 16, 17 and 18, in the same quarterly releases.

That leaves less than a year, and on Heroku much less: Postgres 15 is already deprecated there, new 15 databases stopped on 11 November 2026, and forced upgrades start on 28 January 2027. Elsewhere the community date comes first, followed by the cloud bills in early 2028 and the last distribution patches in late 2028. This page lists those dates, then covers the move to PostgreSQL 18.

What happens on 11 November 2027

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. Four more are scheduled for 15: 11 February, 13 May, 12 August and 11 November 2027, the last of them its final release. If no unscheduled release comes in between, that will be 15.24.

A minor release needs no dump and restore: stop the server, install the new binaries, start it again. Any 15.x can go straight to the latest, which carries every earlier fix, though the notes of each release you skip may ask for extra steps.

The latest is 15.20, released on 12 November 2026 alongside 18.7, 17.12, 16.16 and 14.25, in a batch that fixed 52 security vulnerabilities and over 140 bugs across the supported branches. Its notes ask for more than a restart:

  • 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 bpchar without a length (char(n) is not affected), GiST indexes that use pg_trgm's gist_trgm_ops, and any GIN index you suspect was hit.
  • 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.
  • Coming from 15.18 or earlier, read 15.19 too. 15.19, released on 13 August 2026, limits logical decoding to the output plugins listed in a new setting, output_plugin_libraries, which by default allows only pgoutput and test_decoding. A change-data-capture setup that uses another plugin has to add it after updating. 15.19 also asks you to reindex some btree_gist and ltree indexes.

Managed services apply minor releases on their own schedule. On 17 November 2026, RDS, Aurora, Cloud SQL and Azure all listed 15.19 as their newest 15 minor. RDS commits to a new minor version within 7 days of the community release, Cloud SQL within 30 days and Aurora within 3 months.

After 11 November 2027 the supply stops. A vulnerability found after that date gets fixed in 16 and later, and in 15 only where someone else maintains it.

Who still patches PostgreSQL 15

Where it runs Until What happens after Source
PostgreSQL community 11 November 2027, the scheduled final release No further releases Versioning policy
Heroku Postgres Deprecated since 4 August 2026; end of life 28 February 2027 No new 15 databases since 11 November 2026, though forks and followers are allowed; forced upgrades from 28 January 2027; after 28 February 2027, access restricted and databases deleted, followers included Version support, deprecation
Amazon Linux 2023, postgresql15 (15.19 in the current package list) 11 November 2027 End of support, no further updates AWS
Azure Database for PostgreSQL flexible server Standard support until 11 November 2027 Not announced for 15. 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 2028 Automatic paid extended support until 1 February 2031: $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 29 February 2028 Paid RDS Extended Support from 1 March 2028 to 28 February 2031, for Critical and High CVEs: $0.100 per vCPU-hour in US East (N. Virginia) at today's rates, $0.200 from 1 March 2030. Databases not enrolled are upgraded RDS calendar, Aurora calendar, pricing
RHEL 8, postgresql:15 stream (since 8.8) May 2028 The stream retires; no updates or errata Red Hat
Debian 12, postgresql-15 (the default; 15.20-0+deb12u1 in bookworm-security) 30 June 2028, the end of Debian LTS for 12 No further Debian updates Security tracker, Debian 12
RHEL 9, postgresql:15 stream (since 9.2) November 2028 The stream retires; no updates or errata Red Hat
RHEL 10 Not applicable: Red Hat lists only PostgreSQL 16 and 18 streams Not applicable Application Streams
Ubuntu LTS Not applicable: 22.04 ships 14 and 24.04 ships 16 Not applicable Ubuntu archive
Docker official image postgres:15 Rebuilt as 15.20 on 12 November 2026, last pushed 15 November 2026 Not announced. Docker removed 13 the day after its final release official-images, Docker Hub

Debian 12 and RHEL are the long tail. Plain postgresql installs 15 on Debian 12, and Debian LTS ships each new 15.x as a security update: 15.20-0+deb12u1 is already in bookworm-security. Debian LTS runs to 30 June 2028, and it has patched past a community end before: DLA-4646-1 updated Debian 11's postgresql-13 to 13.23-0+deb11u4, a Debian revision of 13's final release. Red Hat's postgresql:15 stream retires in May 2028 on RHEL 8 and November 2028 on RHEL 9. Each covers its own package only. A server built from apt.postgresql.org or yum.postgresql.org, the PostgreSQL project's own repositories, or a postgres:15 container follows the community date.

No Ubuntu LTS release ships 15. It was only in the interim releases 23.04 and 23.10, both ended. On Ubuntu, 15 comes from apt.postgresql.org.

Amazon Linux 2023 ships 15, 16, 17 and 18 side by side and ends postgresql15 on the community date.

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

What ends first

Heroku, already under way. Heroku supports each major version for three years, not five, and when it releases a new major version it deprecates the third one before it. Postgres 15 was deprecated on 4 August 2026, the day Postgres 18 became generally available on Heroku and its default for new databases. New 15 databases stopped on 11 November 2026, though forks and followers of existing ones are still allowed. Forced upgrades start on 28 January 2027, and after the end of life on 28 February 2027 Heroku starts restricting access and deleting databases still on 15, followers included. Heroku's upgrade commands can take 15 to 16, 17 or 18; 16 is the next one Heroku ends, in Q3 2027, so pass --version 18.

Old minor versions, already. RDS ended standard support for 15.13 and 15.14 on 31 October 2026, no longer lets you create instances on 15.16, and ends 15.15 to 15.17 around March 2027. Aurora ends 15.12 on 30 November 2026, 15.13 on 31 December 2026, 15.14 on 30 April 2027 and 15.15 on 31 May 2027. Aurora's long-term support minor for 15, 15.10, stays in standard support until 29 February 2028 and is so far the only 15 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.

Extensions, already. TimescaleDB 2.29.0, released on 28 July 2026, removed support for 15, about 15 months before its end of life, and asks you to upgrade PostgreSQL before upgrading TimescaleDB. 2.28.3, from 16 July 2026, is the newest release that runs on 15. PostGIS 3.7.0, released on 30 October 2026, still supports 14 to 19, and pgvector supports 13 and newer. Your extensions' release notes are where the real deadline shows up.

Amazon Linux 2023 and Azure, on 11 November 2027. Both stop with the community. AL2023 ends support for postgresql15 that day. Azure lists the same date as the end of standard support, after which it stops patching the engine and refuses new 15 servers. It has set no extended support dates for 15; for 14 it runs standard support to 31 January 2027, then enrolls servers in paid extended support automatically and says the only way to stop the charge is to upgrade.

The bill, from February and March 2028. Cloud SQL enrolls every 15 instance in paid extended support on 1 February 2028, with notifications three months before. RDS and Aurora bill enrolled databases from 1 March 2028, 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 2030. Multi-AZ standbys and read replicas are charged too, and Reserved Instance discounts do not apply.

Forced upgrades, later. RDS upgrades databases with Extended Support disabled on or shortly after 29 February 2028, and attempts to upgrade the rest after Extended Support ends on 28 February 2031. Cloud SQL upgrades 15 instances to its default major version during maintenance from 1 February 2031.

A Docker tag change is not an upgrade. Changing postgres:15 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 exits with an error 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, not the client. Check checksums and replication slots too, because both decide how the upgrade to 18 goes.

SELECT version();
SHOW server_version_num;  -- 150020 means 15.20
SHOW data_checksums;      -- off means the 18 cluster needs initdb --no-data-checksums
SELECT slot_name, slot_type, plugin, active 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 15:

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 15

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

Which version to move to: 18

15 16 17 18
First release 13 Oct 2022 14 Sep 2023 26 Sep 2024 25 Sep 2025
Community end of life 11 Nov 2027 9 Nov 2028 8 Nov 2029 14 Nov 2030
Latest, 17 Nov 2026 15.20 16.16 17.12 18.7
RDS and Aurora standard support 29 Feb 2028 28 Feb 2029 28 Feb 2030 28 Feb 2031
Heroku end of life 28 Feb 2027 Q3 2027 Q3 2028 Q3 2029
Default in Debian 12 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 Debian 12 and Ubuntu 24.04 it comes from apt.postgresql.org.

Skip 16. It buys one year over 15, to 9 November 2028, and Heroku ends it in Q3 2027, before 15's own community date. The exception is RHEL 8, where Red Hat's newest stream is 16, retiring in May 2029; 17 and 18 come from yum.postgresql.org there.

17 is the fallback if an extension or a tool you need is not ready for 18. It is supported until 8 November 2029, and it is what Debian 13 installs, so a Debian 12 server that moves to Debian 13 lands on 17.

PostgreSQL 19 came out on 19 November 2026. 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. With less than a year left on 15, and about three months on Heroku, 18 is the version every platform above runs today.

Jump straight there. postgresql.org says you can upgrade 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, logical replication works across major versions, and RDS lists 18.6 as a direct upgrade target from 15.19.

How to upgrade 15 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/15/bin --new-bindir=/usr/lib/postgresql/18/bin \
  --old-datadir=/srv/pg15 --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 moves the data directories across and can be faster still; the documentation recommends --sync-method=fsync with it. 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. Use the vacuumdb from 18.7 or later: earlier ones let a database owner run SQL as the user running that first command (CVE-2026-116313).

Replication slots do not survive. pg_upgrade migrates logical replication slots and subscriptions only when the old cluster is 17 or later; slots on older clusters are silently ignored. Coming from 15, subscribers and anything that reads changes from a slot, such as a change-data-capture tool, have to be set up again after the upgrade. Once you are on 18, later major upgrades keep them.

Debian 12. Debian 12 has no PostgreSQL newer than 15, so add apt.postgresql.org first. Then pg_upgradecluster -v 18 -m upgrade 15 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, so pass -m upgrade or -m link for the faster route. If you move the server to Debian 13 instead, you get 17: run pg_upgradecluster -v 17 -m upgrade 15 main before removing the 15 packages.

Logical replication gives the shortest outage, which the documentation puts at several seconds. Set wal_level to logical on 15, copy the schema to an 18 server with pg_dump --schema-only, subscribe it to a publication on 15, 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 15 container and restore into a fresh 18 one. For 18, mount the volume at /var/lib/postgresql, not /var/lib/postgresql/data. If 15's checksums are off, 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 from 15.4 or later 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. Upgrade extensions separately.
  • Cloud SQL upgrades in place with pg_upgrade, after an optional precheck, with gcloud sql instances patch <instance> --database-version=POSTGRES_18. For 18 it asks you to upgrade PostGIS to 3.6.0 first, and the upgrade deletes all logical replication slots, so record them beforehand.
  • Azure runs pg_upgrade in place after validation checks, which look for problems such as unsupported extensions. 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). 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 15 and 18

From the "Migration" sections of the 16, 17 and 18 release notes, plus two changes elsewhere in them that affect upgrades and monitoring.

1. Data checksums on by default (18). High, with pg_upgrade. pg_upgrade needs matching checksum settings, and 15's initdb did not enable them by default. If SHOW data_checksums; says off on 15, 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. Settings removed (16 and 17). Medium. vacuum_defer_cleanup_age and promote_trigger_file went in 16, and force_parallel_mode became debug_parallel_query. old_snapshot_threshold, db_user_namespace and trace_recovery_messages went in 17. A postgresql.conf carried over that still sets one stops the new server from starting. Failover scripts that touch a trigger file need pg_ctl promote or pg_promote() instead.

4. Narrower CREATEROLE (16). Medium. A role with CREATEROLE now needs ADMIN OPTION on a role to change it or add members, and can grant CREATEDB, REPLICATION and BYPASSRLS only if it has them. Role inheritance is also fixed per membership at GRANT time. Check tooling that provisions roles.

5. Monitoring views changed (17). Medium. Checkpoint counters moved from pg_stat_bgwriter to the new pg_stat_checkpointer, and buffers_backend and buffers_backend_fsync went in favour of pg_stat_io. 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.

6. Keys on nondeterministic collations (18). 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 18 notes say a pg_dump restore, which pg_upgrade also uses, fails otherwise, so the schema has to change first.

7. 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.

8. 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.

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

Smaller ones: the postmaster symlink is gone, so scripts must call postgres (16); REINDEX DATABASE and reindexdb skip system catalogs (16); the adminpack extension, used by pgAdmin III, was removed (17); 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 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, and PostgreSQL 14 shows what the platforms do once a version's final release is out.

Sources

Common questions

When is PostgreSQL 15 end of life?
On 11 November 2027. The PostgreSQL project supports each major version for five years after its first release, and 15.0 came out on 13 October 2022. Its final minor release is scheduled for 11 November 2027, after which the project publishes no more 15.x fixes, security fixes included.
Is PostgreSQL 15 still supported?
Yes, by the PostgreSQL project, until 11 November 2027. It gets the same bug, security and data corruption fixes as 16, 17 and 18, in the same quarterly releases. The latest is 15.20, released on 12 November 2026. Heroku is the exception: it deprecated Postgres 15 on 4 August 2026, stopped new 15 databases on 11 November 2026 and ends it on 28 February 2027.
When does Amazon RDS stop supporting PostgreSQL 15?
RDS for PostgreSQL keeps 15 in standard support until 29 February 2028. From 1 March 2028, databases enrolled in RDS Extended Support are billed per vCPU-hour, at today's rates $0.100 in US East (N. Virginia), then $0.200 from 1 March 2030. Extended Support for 15 ends on 28 February 2031, and databases not enrolled are upgraded on or shortly after 29 February 2028.
When does Aurora PostgreSQL 15 reach end of life?
Aurora PostgreSQL 15 is in standard support until 29 February 2028, with paid RDS Extended Support from 1 March 2028 to 28 February 2031: $0.100 per vCPU-hour in US East (N. Virginia), $0.200 from 1 March 2030, or $0.085 and then $0.170 per ACU-hour on Aurora Serverless v2. Minor versions end sooner: Aurora 15.12 leaves standard support on 30 November 2026 and 15.13 on 31 December 2026. Its long-term support minor, 15.10, runs to 29 February 2028 and is so far the only 15 minor listed as eligible for Extended Support.
When does Heroku end Postgres 15?
Heroku's end of life for Postgres 15 is 28 February 2027, more than eight months before the community date. Heroku deprecated it on 4 August 2026, the day Postgres 18 became generally available there. New 15 databases stopped on 11 November 2026, though forks and followers of existing ones are still allowed. Forced upgrades start on 28 January 2027, and after 28 February 2027 Heroku starts restricting access and deleting databases still on 15.
Do Google Cloud SQL and Azure still support PostgreSQL 15?
Yes. Cloud SQL keeps 15 in regular support until 1 February 2028, when it enrolls every 15 instance in paid extended support, at $0.07 per vCPU-hour in Iowa and $0.14 in the third year. From 1 February 2031 it upgrades the remaining 15 instances to its default version. Azure Database for PostgreSQL flexible server lists standard support for 15 until 11 November 2027 and has not announced extended support for it.
Which version should I upgrade PostgreSQL 15 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 15 database there in one step. Skip 16: the community supports it only until 9 November 2028, and Heroku ends it in Q3 2027. 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.
Does Debian 12 still patch PostgreSQL 15?
Yes. PostgreSQL 15 is what Debian 12 installs as postgresql, and Debian LTS has already shipped 15.20 to bookworm-security as 15.20-0+deb12u1 (DLA-4905-1). Debian LTS supports Debian 12 until 30 June 2028, past the community date, but that covers Debian's own package only. Debian 12 has no newer PostgreSQL: 18 comes from apt.postgresql.org, and Debian 13 ships 17.
What is the latest version of PostgreSQL 15?
15.20, released on 12 November 2026 with 18.7, 17.12, 16.16 and 14.25. After updating, reindex B-tree indexes on columns declared as bpchar without a length and GiST indexes that use pg_trgm's gist_trgm_ops, and rebuild C-language extensions. On 17 November 2026, RDS, Aurora, Cloud SQL and Azure still listed 15.19 as their newest 15 minor.

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