PostgreSQL Support Lifecycle & End-of-Life Schedule
Official release schedule, active LTS windows, and deprecation dates for PostgreSQL. Avoid running unsupported versions in production.
PostgreSQL Lifecycle Policy Summary
PostgreSQL relational database. Each major version receives five years of active development and security bugfixes from initial release.
Branch Support Matrix & EOL Cutoffs
| Branch / Cycle | Status | Release Date | End of Life (EOL) | Latest Patch | Upgrade Recommendation |
|---|---|---|---|---|---|
| v17 LTS | 🟢 Active Support | 2024-09-26 | 2029-11-08 | 17.3 | ✓ Supported for production |
| v16 LTS | 🟢 Active Support | 2023-09-14 | 2028-11-09 | 16.7 | ✓ Supported for production |
| v15 LTS | 🟢 Active Support | 2022-10-13 | 2027-11-11 | 15.11 | ✓ Supported for production |
| v14 LTS | 🟡 Maintenance Only | 2021-09-30 | 2026-11-12 | 14.16 | Plan upgrade to v17 |
| v13 LTS | 🔴 End of Life (EOL) | 2020-09-24 | 2025-11-13 | 13.20 | ⚠️ Upgrade to v17 |
| v12 | 🔴 End of Life (EOL) | 2019-10-03 | 2024-11-14 | 12.22 | ⚠️ Upgrade to v17 |
Why Upgrading from EOL Versions is Critical
Once an open-source branch reaches End-of-Life, upstream maintainers no longer backport patches for Common Vulnerabilities and Exposures (CVEs). Automated botnets routinely scan for publicly known exploits on unsupported runtime versions.