PostgreSQL End of Life Dates
Release, end of support and end of life dates for every tracked PostgreSQL version, with current status.
All products | Vendor lifecycle page | Source entry
Coverage note: some values are retained from earlier reviews. Unresolved releases or dates may be omitted; feed retrieval is not verification of every displayed value.
Status calculated for 2026-11-04: 29 versions tracked; 4 supported, 0 security fixes only, 1 ending within 90 days, 24 end of life. Calculated from the dates stored here, not a vendor verification date. With JavaScript on, the calculation uses today's date.
Swipe the table sideways to see all columns ->
| Version | Status | Released | Support ends | Latest |
|---|---|---|---|---|
| 18 | Supported | 2025-09-25 | 2030-11-14 | 18.6 |
| 17 | Supported | 2024-09-26 | 2029-11-08 | 17.11 |
| 16 | Supported | 2023-09-14 | 2028-11-09 | 16.15 |
| 15 | Supported | 2022-10-13 | 2027-11-11 | 15.19 |
| 14 | Ends within 90 days | 2021-09-30 | 2026-11-12 | 14.24 |
| 13 | End of life | 2020-09-24 | 2025-11-13 | 13.23 |
| 12 | End of life | 2019-10-03 | 2024-11-21 | 12.22 |
| 11 | End of life | 2018-10-18 | 2023-11-09 | 11.22 |
| 10 | End of life | 2017-10-05 | 2022-11-10 | 10.23 |
| 9.6 | End of life | 2016-09-29 | 2021-11-11 | 9.6.24 |
| 9.5 | End of life | 2016-01-07 | 2021-02-11 | 9.5.25 |
| 9.4 | End of life | 2014-12-18 | 2020-02-13 | 9.4.26 |
| 9.3 | End of life | 2013-09-09 | 2018-11-08 | 9.3.25 |
| 9.2 | End of life | 2012-09-10 | 2017-11-09 | 9.2.24 |
| 9.1 | End of life | 2011-09-12 | 2016-10-27 | 9.1.24 |
| 9.0 | End of life | 2010-09-20 | 2015-10-08 | 9.0.23 |
| 8.4 | End of life | 2009-07-01 | 2014-07-24 | 8.4.22 |
| 8.3 | End of life | 2008-02-04 | 2013-02-07 | 8.3.23 |
| 8.2 | End of life | 2006-12-05 | 2011-12-05 | 8.2.23 |
| 8.1 | End of life | 2005-11-08 | 2010-11-08 | 8.1.23 |
| 8.0 | End of life | 2005-01-19 | 2010-10-01 | 8.0.26 |
| 7.4 | End of life | 2003-11-17 | 2010-10-01 | 7.4.30 |
| 7.3 | End of life | 2002-11-27 | 2007-11-27 | 7.3.21 |
| 7.2 | End of life | 2002-02-04 | 2007-02-04 | 7.2.8 |
| 7.1 | End of life | 2001-04-13 | 2006-04-13 | 7.1.3 |
| 7.0 | End of life | 2000-05-08 | 2005-05-08 | 7.0.3 |
| 6.5 | End of life | 1999-06-09 | 2004-06-09 | 6.5.3 |
| 6.4 | End of life | 1998-10-30 | 2003-10-30 | 6.4.2 |
| 6.3 | End of life | 1998-03-01 | 2003-03-01 | 6.3.2 |
Frequently asked questions
Which PostgreSQL versions are still supported?
Using the dates stored here, status calculated for 2026-11-04 shows 5 of 29 tracked PostgreSQL versions are still in support (18, 17, 16, 15, 14). The table above shows the calculated status of every tracked version; retained values may still need vendor confirmation.
What is the newest PostgreSQL version tracked here?
18 (latest update 18.6), released 2025-09-25. This is the newest release included here, not necessarily the newest vendor release. Unresolved releases may be omitted while their dates or support status are checked. See the linked vendor source for current releases.
Where do these PostgreSQL dates come from?
From the vendor sources linked at the top of this page (vendor lifecycle page) and the source entry. Vendors can revise dates, so confirm there before you schedule a migration.
Planning notes
The PostgreSQL Global Development Group releases a new major version about once a year and supports each major version for 5 years after its initial release. After that, a final minor version is released and the major version is end-of-life. Between those dates, each major version gets bug fixes and security fixes in minor releases at least once every three months.
Minor upgrades do not need a dump and restore: you stop the server, install the new binaries and restart. The project recommends always running the current minor release of your major version and considers that less risky than staying on an old minor. Major upgrades do need a dump/reload or pg_upgrade, and you can skip intervening majors if you read their release notes first.
For planning, count back from the Final Release date in the table above, leave time for a staging run of pg_upgrade, and check extension and driver compatibility before the move.
Sources: PostgreSQL versioning policy.
Note: "Not announced" means no confirmed date is shown here; check the linked vendor source. "Ended (no date published)" means the source marks it ended without a date. Dates are compared as calendar days in your own time zone. A published end date counts as the last day of support.
Data: endoflife.date (MIT license), feed retrieved 2026-11-04. Retrieval does not mean every displayed value was verified that day. Some values are retained from earlier reviews, and unresolved releases or dates may be omitted. Confirm with the linked vendor source before a purchase or migration decision.