PostgreSQL 18 End of Life (EOL): November 2030, Where It Runs and What Changed
PostgreSQL 18 is supported until 14 November 2030. 19 came out on 19 November 2026, but 18 is still the default on Cloud SQL, Heroku, Ubuntu 26.04 and Docker, and the version to upgrade 15, 16 and 17 to. Where it runs, what ends first, and what changes when you arrive.
Written Updated Shahzeb Umer
SubscribeStatus
Supported
Support ends .
- Time left
- 1456 days
- Latest release
- 18.7
- Support type
- Standard
5.1 years of support
- Supported25 Sep 2025 – 14 Nov 2030
Supported for 5.1 years, from 25 Sep 2025 to 14 Nov 2030.
Who still patches it
Nine places PostgreSQL 18 runs, seven deadlines.
- PostgreSQL (community): Final release 14 Nov 2030
- Amazon Linux 2023 (postgresql18): Ends with AL2023, 30 Jun 2029
- Heroku Postgres (default): End of life Q3 2029
- Azure flexible server: Standard support to 14 Nov 2030
- RHEL 9.8+, 10.2+ (PostgreSQL 18 stream): Patched to Nov 2030
- Amazon RDS, Aurora: Extended Support to Feb 2034
- Ubuntu 26.04 (postgresql-18, default): Ubuntu Pro to May 2036
- Google Cloud SQL (default): No end date listed yet
- Docker image (postgres:18, latest): Still rebuilt, no end announced
Where to move
Be on PostgreSQL 18.
The short version
- PostgreSQL 18 reaches end of life on 14 November 2030, the date of its scheduled final release. 18.0 came out on 25 September 2025 and the latest release, 18.7, on 12 November 2026. PostgreSQL 19 came out on 19 November 2026, but no managed service offers it yet.
- It runs nearly everywhere: on RDS since 14 November 2025 and Aurora since 11 June 2026, as the default on Cloud SQL, Heroku, Ubuntu 26.04 and Docker's
latest, on Azure, and as a RHEL 9.8 and 10.2 stream. Amazon Linux 2023 stops updating it on 30 June 2029 and Heroku ends it in Q3 2029; RDS and Aurora standard support runs to 28 February 2031. - On 15 or 16, move to 18 now rather than wait for 19, which managed services add weeks to months after release. On 17 you can choose. Already on 18, nothing is due before mid-2029. Coming from 16 or 17, check data checksums before pg_upgrade, and expect MD5 warnings and new asynchronous I/O settings.
On this page
PostgreSQL 18 reaches end of life on 14 November 2030. That is the scheduled date of its final release on postgresql.org, five years after 18.0 came out on 25 September 2025. Until then it gets bug, security and data corruption fixes in the quarterly minor releases.
PostgreSQL 19 came out on 19 November 2026, but 18 is still the newest version most platforms offer and the one they default to, and it keeps four more years of fixes. This page covers where 18 runs and until when, what ends first, whether 19 is worth waiting for, and what changes when you arrive from 16 or 17.
How long PostgreSQL 18 is supported
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. That leaves about sixteen more 18.x releases, the last on 14 November 2030. Each one installs over the last without a dump and restore.
The latest is 18.7, from 12 November 2026. Like 17.12 and 16.16 the same day, it asks you to reindex B-tree indexes on bpchar columns declared without a length, GiST indexes using pg_trgm's gist_trgm_ops and any GIN index you suspect was damaged, to take a new full backup if you use incremental backups, and to rebuild C extensions for full protection against CVE-2026-6460. Three of its notes concern 18 alone:
- Use vacuumdb from 18.7. Before 18.7, the
vacuumdb --missing-stats-onlyrun that the pg_upgrade documentation recommends let a database owner execute SQL as the user running vacuumdb (CVE-2026-116313). Earlier major versions do not have that option and are not affected. - io_uring users get a leak fix. With
io_method=io_uring, resources leaked across crash restarts until a restart eventually failed with "too many open files" or a similar error. The default,worker, was not affected. - Check partitioned tables for
NOT NULL NO INHERIT. 18 is the first version to store NOT NULL constraints inpg_constraint, and 18.7 closes a gap that could let a partition hold nulls it should not. The release notes give the query to find affected constraints:
SELECT conrelid::regclass, conname
FROM pg_constraint
WHERE contype = 'n' AND connoinherit
AND conrelid IN (SELECT oid FROM pg_class WHERE relkind = 'p');
Drop the ones you do not want, and repair the ones you do with ALTER TABLE ... ALTER CONSTRAINT ... INHERIT, which fails if a partition already holds nulls.
TimescaleDB 2.32.0, released the same day, is compatible only up to 18.6 and asks you to install 2.32.1 before updating PostgreSQL past it. As of 17 November 2026, 2.32.1 is not out.
Where PostgreSQL 18 runs
| Where | Offers 18 | Supported until | After that | Source |
|---|---|---|---|---|
| PostgreSQL community | 18.0 on 25 September 2025; 18.7 now | 14 November 2030, the scheduled final release | No further releases | Versioning policy |
Amazon Linux 2023, postgresql18 |
18.6 in the current package list | 30 June 2029, when AL2023 ends | No further updates from AWS | AWS |
| Heroku Postgres | Generally available and the default since 4 August 2026 | End of life Q3 2029 | Deprecated when Heroku Postgres 21 ships; forced upgrades scheduled after five months, databases deleted after six | Heroku, changelog |
| Azure Database for PostgreSQL flexible server | Standard support from 25 September 2025; new servers get 18.6 | 14 November 2030 | Not announced | Version policy, supported versions |
| RHEL 9.8 and later, RHEL 10.2 and later, PostgreSQL 18 stream | Since May 2026 | November 2030 | The stream retires; no updates or errata | Red Hat |
| Amazon RDS for PostgreSQL | Since 14 November 2025; newest minor 18.6 | Standard support until 28 February 2031 | Paid RDS Extended Support to 28 February 2034: $0.100 per vCPU-hour in US East (N. Virginia) at today's rates, $0.200 from 1 March 2033 | RDS calendar, pricing |
| Aurora PostgreSQL | Since 11 June 2026, starting at 18.3; newest minor 18.6 | Standard support until 28 February 2031 | The same Extended Support dates and prices for provisioned instances; no long-term support minor named yet | Aurora calendar, pricing |
Ubuntu 26.04 LTS, postgresql-18 in main (the default; 18.6 on 17 November) |
Since 23 April 2026 | Standard security maintenance until May 2031 | Ubuntu Pro coverage until May 2036 | Release cycle, package |
| Google Cloud SQL for PostgreSQL | Generally available since 20 November 2025, now the default; 18.6 | No date listed yet | Cloud SQL's rule is paid extended support from three months after community end of life | Versions, release notes, extended support |
| Debian | Not in a stable release: Debian 13 ships 17, and 18 is in testing and unstable | Not applicable | apt.postgresql.org builds 18.7 for Debian 13 | Debian archive |
Docker official image postgres:18 |
latest since 25 September 2025; rebuilt as 18.7 on 12 November 2026 |
No end announced | Not announced | official-images |
Most platforms run one minor release behind. On 17 November 2026, RDS, Aurora, Cloud SQL, Azure, Amazon Linux 2023 and Ubuntu 26.04 all had 18.6 as their newest 18 build, while the Docker image and the PostgreSQL project's apt and yum repositories had 18.7. RDS commits to new minor versions within 7 days of the community release and Aurora within 3 months, and Azure and Cloud SQL roll them out in maintenance windows.
Ubuntu 26.04 has a kernel caveat. Ubuntu 26.04 installs 18 as plain postgresql, and its release notes warn that a change in Linux 7.0 "may cause a significant throughput and latency regression" for PostgreSQL. Systems using huge pages are not affected, so Canonical says to set huge_pages to on. 26.04's PostgreSQL 18 also no longer builds for i386. On Ubuntu 24.04, whose archive has 16, apt.postgresql.org provides 18.7.
Red Hat skipped 17 for it. RHEL 9 and 10 go from a PostgreSQL 16 stream to an 18 stream, added in RHEL 9.8 and 10.2 and supported until November 2030, the month of the community end. RHEL 10's default stays 16.
What ends first
The latest tag, when 19 reaches Docker. Docker moved the official image's latest tag to 18 on 25 September 2025, the day 18.0 came out. On 19 November 2026, 19.0's release day, latest still pointed to 18.7, with a pull request open to publish 19.0 and move latest to it. Once it moves, anything that pulls postgres or postgres:latest gets 19 on its next pull, and the 19 image, like 18's, exits with an error when it finds data from another major version under /var/lib/postgresql. Pin postgres:18. Heroku has the same trap: pg:upgrade without --version goes to the newest version Heroku offers.
Old minor versions. RDS ends standard support for 18.1 to 18.3 in March 2027 and for 18.4 and 18.6 in September 2027, and marks 18.2 as closed to new instances. Aurora ends 18.3 on 30 November 2027, 18.4 on 31 December 2027 and 18.6 on 28 February 2028. Aurora has named no long-term support minor for 18 yet; it promises one within 12 months of a major version's Aurora release, which for 18 means by June 2027.
Amazon Linux 2023, on 30 June 2029. AWS stops updating postgresql18, with the rest of AL2023, about 16 months before the community date.
Heroku, in Q3 2029. Heroku supports each major version for three years, not five, and deprecates the third major version before each new one. By that rule 18 goes when Heroku Postgres 21 ships, and Heroku's version page lists its end of life as Q3 2029.
Extensions. TimescaleDB dropped 14 and 15 about 15 to 18 months before their community end dates; at that pace, its support for 18 would end in 2029. On Cloud SQL, upgrading to 18 needs PostGIS 3.6.0 first. On Azure, an in-place upgrade to 18 is blocked while azure_ai, azure_storage, pg_diskann or pgrouting is installed.
The bill, from 2031. RDS and Aurora charge enrolled databases from 1 March 2031, and RDS enrolls a database by default when it is created through the AWS CLI, the API or CloudFormation. Aurora Serverless v2 pays per ACU-hour, at today's US East (N. Virginia) rates $0.085, then $0.170. Cloud SQL lists no extended support date for 18 yet: its rule enrolls a version three months after community end of life, and for 14 to 17 that has meant 1 February. Azure lists standard support until 14 November 2030.
How to check what you run
Ask the server. Two settings tell you how it was built and how it reads from disk.
SELECT version();
SHOW server_version_num; -- 180007 means 18.7
SHOW data_checksums; -- on for clusters created by 18's initdb
SHOW io_method; -- worker unless someone changed it
For containers, find out what latest means today and which files rely on it:
docker run --rm postgres:latest postgres --version
docker ps --format '{{.Names}}\t{{.Image}}' | grep -i postgres
grep -rnE 'image: *postgres(:latest)? *$' --include='*.yml' --include='*.yaml' .
grep -rnE '^FROM +postgres(:latest)?( |$)' --include='Dockerfile*' .
On AWS, ask for the support dates of 18 and the Aurora 18 versions you can create:
aws rds describe-db-major-engine-versions --engine postgres --major-engine-version 18
aws rds describe-db-engine-versions --engine aurora-postgresql \
--query 'DBEngineVersions[?starts_with(EngineVersion, `18`)].EngineVersion' --output text
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>
Should you wait for PostgreSQL 19?
| You run | Community end of life | What ends first | Move to |
|---|---|---|---|
| 15 | 11 Nov 2027 | Heroku, 28 Feb 2027 | 18, now |
| 16 | 9 Nov 2028 | Heroku, Q3 2027 | 18, now |
| 17 | 8 Nov 2029 | Heroku, Q3 2028 | 18, or 19 once your platform has it |
| 18 | 14 Nov 2030 | Amazon Linux 2023, 30 Jun 2029 | 19 or later, by mid-2029 |
19 adds a year, not a different kind of support. PostgreSQL 19 came out on 19 November 2026 and is supported until November 2031, a year longer than 18.
Managed services take weeks to months. 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 that meant RDS on 14 November 2025, Cloud SQL on 20 November 2025, Aurora on 11 June 2026 and Heroku on 4 August 2026, from seven weeks to ten months after 18.0.
So on 15 or 16, do not wait. Heroku ends 15 in February 2027 and 16 in Q3 2027, before 19 is likely to reach every managed service, and 18 is available everywhere today. On 17 you have until late 2029, so skipping 18 can save an upgrade; PostgreSQL 17 weighs it. On 18, take 19 when your extensions and platform are ready. Its release notes warn pg_upgrade users with full text search, pg_trgm or fuzzystrmatch indexes that they may need to reindex.
Upgrading to 18 from 15, 16 or 17
pg_upgrade takes any cluster from 9.2 on to 18 in one step, and postgresql.org says you can skip major versions as long as you read the release notes of the ones you skip. RDS lists 18.6 as a direct target from both 16.15 and 17.11. Three things are new in 18's pg_upgrade:
- Statistics come across. Most optimizer statistics are transferred, though not those created with
CREATE STATISTICS, so the new cluster plans well sooner. Finish withvacuumdb --all --analyze-in-stages --missing-stats-only, thenvacuumdb --all --analyze-only, using vacuumdb from 18.7. --swapmode moves the data directories instead of copying or linking files. It can be the fastest mode, especially with many relations, but the old cluster is unsafe to start once the transfer begins.- Parallel checks.
--jobsnow also runs the per-database checks in parallel.
Before you start, settle checksums (below), install your extensions' 18 builds, and look for keys on nondeterministic collations, which now block the restore step. Logical replication slots and subscriptions survive pg_upgrade only from 17 or later; from 15 or 16, subscribers and change-data-capture slots have to be set up again.
The detailed routes, from pg_upgrade and pg_upgradecluster to RDS blue/green deployments, Cloud SQL, Azure, Heroku and Docker, are on PostgreSQL 17 for 17 and PostgreSQL 16 for 16. One Docker point matters on every route: 18 images keep their data in /var/lib/postgresql/18/docker under a volume at /var/lib/postgresql, not in /var/lib/postgresql/data.
What changes when you arrive on 18
From the 18.0 release notes, with what the platforms allow.
Data checksums are on for new clusters. 18's initdb enables them unless you pass --no-data-checksums, and the 18 Docker image runs initdb with its defaults. A cluster brought over by pg_upgrade keeps the old setting, because pg_upgrade needs both sides to match, so a 17 or 16 cluster that never had checksums still lacks them after the upgrade. pg_checksums --enable adds them offline: the server must be shut down cleanly, it can take a long time on a large cluster, and standbys should be rebuilt or switched at the same time.
Asynchronous I/O is new, and on. 18 reads ahead through an asynchronous I/O subsystem that the release notes say can speed up sequential scans, bitmap heap scans and vacuum. io_method chooses how: worker, the default, uses background processes (io_workers, 3 by default); io_uring needs a build with liburing; sync turns it off. It can only be set at server start. effective_io_concurrency and maintenance_io_concurrency now default to 16. The platforms differ: Aurora does not expose io_method, io_workers or io_max_concurrency and uses its own asynchronous I/O, Azure does not allow io_method = io_uring, and Cloud SQL offers all three as database flags.
MD5 passwords are deprecated. CREATE ROLE and ALTER ROLE warn when they set an MD5 password, and support goes in a future major version. Set password_encryption to scram-sha-256 and reset the affected passwords; md5_password_warnings = off hides the warning in the meantime.
Defaults that change query and tool output. Generated columns are now virtual, computed when read, unless you write STORED. EXPLAIN ANALYZE includes buffer counts without being asked. VACUUM and ANALYZE on a parent table also process its inheritance children, unless you add ONLY. RESTRICT foreign key violations report SQLSTATE 23001 instead of 23503.
Monitoring views moved. pg_stat_wal lost its write and sync columns, and WAL timing now appears in pg_stat_io, which reports bytes in new read_bytes, write_bytes and extend_bytes columns instead of op_bytes. NOT NULL constraints now appear in pg_constraint, which tools that read that catalog will notice.
New things worth using. uuidv7() generates timestamp-ordered UUIDs. Skip scan lets multicolumn B-tree indexes serve queries that do not filter on the leading column. pg_hba.conf gains an oauth authentication method. Wire protocol 3.2 brings 256-bit cancel keys, for clients that support it.
From 16, 17's changes too. Maintenance commands run index and materialized view functions with a safe search_path, checkpoint counters moved from pg_stat_bgwriter to pg_stat_checkpointer, and old_snapshot_threshold, db_user_namespace, trace_recovery_messages and the adminpack extension are gone. PostgreSQL 16 lists them with what to do.
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
- Versioning policy, roadmap, the November 2026 release, the 18.7 release notes and CVE-2026-116313: support policy, end dates, the latest 18 release and the 19 schedule
- Release notes for 17 and 18, resource settings, pg_upgrade, pg_checksums and upgrading logical replication clusters: what changed in 18 and how to upgrade
- AWS: RDS and Aurora calendars, Aurora 18.3 release notes, Aurora LTS releases, Extended Support, enrollment, RDS pricing, Aurora pricing and major upgrades
- Google Cloud: versions, release notes, extended support and in-place upgrades
- Azure: version policy, supported versions and major version upgrades
- Heroku: version support, Postgres 18 general availability and upgrading
- Distributions: Ubuntu release cycle, Ubuntu 26.04 release notes, Ubuntu package, Red Hat Application Streams, Amazon Linux 2023 packages, Debian archive, apt.postgresql.org and yum.postgresql.org
- Docker official images, the
latestmove to 18 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 18 end of life?
Is PostgreSQL 18 the latest version?
Which cloud providers support PostgreSQL 18?
When does Amazon RDS stop supporting PostgreSQL 18?
Should I wait for PostgreSQL 19 instead of upgrading to 18?
Is PostgreSQL 18 stable?
Do I need to disable data checksums to upgrade to PostgreSQL 18?
When does PostgreSQL 15 reach end of life?
How long will Heroku support Postgres 18?
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