PostgreSQL (postgres, pgsql) End of Life
PostgreSQL Global Development Group
| Version | Released | Final Release | Status |
|---|---|---|---|
| 18 | 25 Sep 2025 | 14 Nov 2030 | Supported 1,564 days left |
| 17 | 26 Sep 2024 | 8 Nov 2029 | Supported 1,193 days left |
| 16 | 14 Sep 2023 | 9 Nov 2028 | Supported 829 days left |
| 15 | 13 Oct 2022 | 11 Nov 2027 | Supported 465 days left |
| 14 | 30 Sep 2021 | 12 Nov 2026 | Ending Soon 101 days left |
| 13 | 24 Sep 2020 | 13 Nov 2025 | End of Life 263 days ago |
| 12 | 3 Oct 2019 | 21 Nov 2024 | End of Life 620 days ago |
Support policy
The PostgreSQL project supports each major version for five years after its initial release. Minor releases are issued roughly quarterly and contain only bug and security fixes; upgrading to the current minor release is always recommended.
Notes
PostgreSQL has an unusually simple life cycle: a single phase of five years from the initial release. There is no separate "feature updates end" and "security updates end" split as with Windows Server or RHEL — the final minor release ships on the end date.
Major releases land each September or October, and support ends five years later in
November. A major upgrade requires pg_upgrade or a dump/restore, not the drop-in
replacement that minor updates allow. Five years is short for a database, so expect at
least one major upgrade during a typical system's operational life.
Minor releases contain only bug fixes, security fixes and data corruption fixes. The project states explicitly that performing minor upgrades is less risky than continuing to run an old minor version.
Managed services (Amazon RDS, Azure Database) and distribution packages sometimes offer extended support beyond these dates. Check your provider's life cycle separately.
Sources
Last verified: 2026-08-04