What end of life means
With each end of life the community publishes one last minor release and then stops. For PostgreSQL 14 no more security or bug fixes will appear after 12 November 2026, for PostgreSQL 15 none after 11 November 2027. The database keeps working, but new vulnerabilities stay open. Run the latest minor release of your version in the meantime, and plan the major upgrade.
Which version to choose
PostgreSQL 18 is supported until 14 November 2030 and is offered by all large cloud providers. PostgreSQL 19 was released on 19 November 2026 and is supported until 19 November 2031, but cloud services and extensions usually need some months to support a new major version. For most upgrades from 14 or 15, PostgreSQL 18 is the safe choice today. You do not need to pass through the intermediate versions, but do read the release notes of every version you skip.
How to upgrade
- pg_upgrade: upgrades the data directory in place, usually in minutes with the link option. Since PostgreSQL 18 it also keeps the optimizer statistics, so performance after the upgrade is normal straight away.
- Dump and restore:
pg_dumpandpg_restoreinto a new server. Simple and safe, but the downtime grows with the size of the database. - Logical replication: a new server on the new version is kept in sync, and you switch over in seconds. The best route for large databases with little room for downtime.
What changes since 14
- From PostgreSQL 15, ordinary users can no longer create objects in the
publicschema of a new database. An upgrade keeps the existing permissions, but new databases and scripts that create them notice the difference. - PostgreSQL 15 removed the exclusive backup mode:
pg_start_backup()andpg_stop_backup()becamepg_backup_start()andpg_backup_stop(). Old backup scripts fail. - PostgreSQL 15 removed PL/Python for Python 2 (
plpythonu,plpython2u). - PostgreSQL 18 deprecates MD5 passwords: move accounts to SCRAM-SHA-256.
- Since PostgreSQL 18
initdbturns on data checksums by default, and pg_upgrade needs matching settings: an old cluster without checksums needs a new cluster created with--no-data-checksums, or checksums enabled first. - Extensions must be available in the new version; check every extension in use.
Managed services: the cloud deadlines
- Amazon RDS and Aurora PostgreSQL: standard support for PostgreSQL 14 ends on 28 February 2027, for 15 on 29 February 2028. Instances still running then are enrolled in paid RDS Extended Support, charged per vCPU per hour and more expensive from the third year, for up to three years. After that RDS upgrades them automatically.
- Azure Database for PostgreSQL: standard support for 14 ends on 31 January 2027. Servers are then enrolled automatically in paid extended support, which for 14 runs until 11 November 2029; the only way out is an upgrade.
- Google Cloud SQL for PostgreSQL: extended support for 14 starts on 1 February 2027 and for 15 on 1 February 2028, and is charged for versions past their end of life.
In each case the extended period is for planning the upgrade, not for avoiding it.
How the free scan helps
The MigrateMyDatabase scan has a read-only script for PostgreSQL that collects the structure of your database: tables, columns, indexes, functions, extensions and settings. Paste the result, choose PostgreSQL 18 on your own server or on a managed service, and see what needs attention per target. The analysis runs in your browser and nothing is uploaded.
Questions
Is PostgreSQL 14 still supported?
Not by the community: PostgreSQL 14 reached its end of life on 12 November 2026. Cloud providers keep it running for a while, partly with paid extended support.
When does PostgreSQL 15 reach end of life?
On 11 November 2027, five years after its first release.
Can I upgrade from PostgreSQL 14 straight to 18?
Yes. pg_upgrade, dump and restore and logical replication can all skip versions. Read the release notes of 15, 16, 17 and 18 for incompatible changes.
What happens to my RDS instance on PostgreSQL 14 after 28 February 2027?
It is enrolled in RDS Extended Support and charged for it from 1 March 2027. Extended Support for 14 ends on 28 February 2030; after that RDS upgrades the instance automatically.
Check your PostgreSQL 14 or 15 database before the upgrade: run the read-only script, paste the result and pick PostgreSQL 18 or a managed service as the target. Free, and nothing leaves your browser.
Start the free scan