PostgreSQL 14 End of Life: November 12, 2026 — the Clock Is Running
PostgreSQL 14 end date: November 12, 2026 — the day of PostgreSQL 14's final scheduled release, after which it receives no security or bug fixes of any kind.
PostgreSQL 14 reaches end of life on November 12, 2026. After that date it receives no further releases of any kind — no security fixes, no data-corruption fixes — from the PostgreSQL Global Development Group. PostgreSQL's policy is famously exact: five years of support per major version, with final releases in November. PostgreSQL 13 died last November; 14 is next; 15 follows in November 2027.
That November rhythm makes PostgreSQL one of the most plannable databases in existence — and every November, a wave of production databases misses the memo anyway. PostgreSQL 14 shipped in 2021 and sits under an enormous share of applications built in the 2021–2023 cycle. If yours is among them, the practical deadline isn't November — it's whenever your last maintenance window before November falls.
Key Dates at a Glance
- PostgreSQL 18: end of life 2030-11-14
- PostgreSQL 17: end of life 2029-11-08
- PostgreSQL 16: end of life 2028-11-09
- PostgreSQL 15: end of life 2027-11-11
- PostgreSQL 14: end of life 2026-11-12
- PostgreSQL 13: end of life 2025-11-13
PostgreSQL End-of-Life Table (every version)
Every PostgreSQL major release with its release date, end-of-life date, current status, and latest point release — generated from the same dataset behind endoflife.ai/postgresql.
| Version | Released | End of life | Status | Latest release |
|---|---|---|---|---|
| PostgreSQL 18 | Sep 25, 2025 | Nov 14, 2030 | Supported | 18.4 (May 11, 2026) |
| PostgreSQL 17 | Sep 26, 2024 | Nov 8, 2029 | Supported | 17.10 (May 11, 2026) |
| PostgreSQL 16 | Sep 14, 2023 | Nov 9, 2028 | Supported | 16.14 (May 11, 2026) |
| PostgreSQL 15 | Oct 13, 2022 | Nov 11, 2027 | Supported | 15.18 (May 11, 2026) |
| PostgreSQL 14 | Sep 30, 2021 | Nov 12, 2026 | Supported | 14.23 (May 11, 2026) |
| PostgreSQL 13 | Sep 24, 2020 | Nov 13, 2025 | EOL | 13.23 (Nov 10, 2025) |
| PostgreSQL 12 | Oct 3, 2019 | Nov 21, 2024 | EOL | 12.22 (Nov 18, 2024) |
| PostgreSQL 11 | Oct 18, 2018 | Nov 9, 2023 | EOL | 11.22 (Nov 6, 2023) |
| PostgreSQL 10 | Oct 5, 2017 | Nov 10, 2022 | EOL | 10.23 (Nov 7, 2022) |
| PostgreSQL 9.6 | Sep 29, 2016 | Nov 11, 2021 | EOL | 9.6.24 (Nov 8, 2021) |
| PostgreSQL 9.5 | Jan 7, 2016 | Feb 11, 2021 | EOL | 9.5.25 (Feb 8, 2021) |
| PostgreSQL 9.4 | Dec 18, 2014 | Feb 13, 2020 | EOL | 9.4.26 (Feb 10, 2020) |
| PostgreSQL 9.3 | Sep 9, 2013 | Nov 8, 2018 | EOL | 9.3.25 (Nov 5, 2018) |
| PostgreSQL 9.2 | Sep 10, 2012 | Nov 9, 2017 | EOL | 9.2.24 (Nov 6, 2017) |
| PostgreSQL 9.1 | Sep 12, 2011 | Oct 27, 2016 | EOL | 9.1.24 (Oct 24, 2016) |
| PostgreSQL 9.0 | Sep 20, 2010 | Oct 8, 2015 | EOL | 9.0.23 (Oct 5, 2015) |
| PostgreSQL 8.4 | Jul 1, 2009 | Jul 24, 2014 | EOL | 8.4.22 (Jul 21, 2014) |
| PostgreSQL 8.3 | Feb 4, 2008 | Feb 7, 2013 | EOL | 8.3.23 (Feb 4, 2013) |
| PostgreSQL 8.2 | Dec 5, 2006 | Dec 5, 2011 | EOL | 8.2.23 (Dec 1, 2011) |
| PostgreSQL 8.1 | Nov 8, 2005 | Nov 8, 2010 | EOL | 8.1.23 (Dec 13, 2010) |
| PostgreSQL 8.0 | Jan 19, 2005 | Oct 1, 2010 | EOL | 8.0.26 (Oct 1, 2010) |
| PostgreSQL 7.4 | Nov 17, 2003 | Oct 1, 2010 | EOL | 7.4.30 (Oct 1, 2010) |
| PostgreSQL 7.3 | Nov 27, 2002 | Nov 27, 2007 | EOL | 7.3.21 (Jan 3, 2008) |
| PostgreSQL 7.2 | Feb 4, 2002 | Feb 4, 2007 | EOL | 7.2.8 (May 9, 2005) |
| PostgreSQL 7.1 | Apr 13, 2001 | Apr 13, 2006 | EOL | 7.1.3 (Aug 17, 2001) |
| PostgreSQL 7.0 | May 8, 2000 | May 8, 2005 | EOL | 7.0.3 (Nov 12, 2000) |
| PostgreSQL 6.5 | Jun 9, 1999 | Jun 9, 2004 | EOL | 6.5.3 (Nov 4, 1999) |
| PostgreSQL 6.4 | Oct 30, 1998 | Oct 30, 2003 | EOL | 6.4.2 (Jan 3, 1999) |
| PostgreSQL 6.3 | Mar 1, 1998 | Mar 1, 2003 | EOL | 6.3.2 (Apr 18, 1998) |
Per-version pages: endoflife.ai/postgresql · Broader guide: PostgreSQL EOL dates for every version.
Upgrading off 14: what actually matters
- Target 17 or 18, not 15 — 15 has just one more year than 14 (to November 2027), and even 16 only runs to November 2028. PostgreSQL 17 is supported to November 2029 and 18 to November 2030, so the same upgrade effort buys three to four more years. If your extensions are ready for it, 18 is the longest runway PostgreSQL currently ships.
- pg_upgrade makes the jump manageable — in-place major upgrades with minutes of downtime are routine now; logical replication offers near-zero-downtime paths for the estates that need them.
- Extensions are the real critical path — PostGIS, timescale, and friends need matching builds on the target version; check them before scheduling anything.
- Managed-cloud users: your clock differs. RDS, Cloud SQL and friends run their own (usually later) deprecation schedules with forced-upgrade phases — check your provider's date, not just upstream's, but don't confuse their grace period with support.
If November is impossible
Third-party PostgreSQL support vendors patch EOL majors past upstream's cutoff — a legitimate bridge for the application that can't re-certify in time. As always: a bridge with an end date, not a destination. The options, compared.
PostgreSQL currently carries an EOL Risk Score™ of 60/100 — Grade C, elevated risk, recalculated at every site build from EOL recency, attack surface, CISA KEV exposure, and extended-support availability. Per-version scores and dates are on the PostgreSQL lifecycle page.
The right response comes down to one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support fees paid repeatedly cost more than doing the project once. Indefinitely, migrate now and plan the next one before it surprises you. Extended support is often the more expensive choice over a multi-year horizon — a bridge, not a destination. And if this deadline feels like vendor caprice, it isn’t — why end of life is inevitable for every version, with the receipts.
Frequently Asked Questions
When does PostgreSQL 14 reach end of life?
November 12, 2026. Per the PostgreSQL Global Development Group's five-year policy, the final PostgreSQL 14 point release ships that day, and no further security or bug fixes follow — including fixes for data-corruption bugs.
Which PostgreSQL versions are supported after November 2026?
PostgreSQL 15 (until November 2027), 16 (November 2028), 17 (November 2029), and 18 (November 2030). Each major gets exactly five years, with EOL falling in November.
Should I upgrade PostgreSQL 14 to 15, or jump further?
Jump further. PostgreSQL 15 reaches EOL just one year after 14 (November 2027), so upgrading 14→15 buys minimal time for the same effort. Most estates should target 16 or 17, checking extension compatibility first.
What if I can't upgrade PostgreSQL 14 before November 2026?
Third-party PostgreSQL support vendors offer patching for EOL majors beyond upstream's cutoff — a workable bridge while an upgrade or re-certification completes. Managed cloud providers (RDS, Cloud SQL) also run their own later deprecation schedules, but those end in forced upgrades, not indefinite support.