PostgreSQL 16 End of Life
Support dates, the patch stream you lose at EOL, and upgrade guidance — rebuilt from live data.
PostgreSQL 16 is actively supported. It reaches end of life on 9 Nov 2028.
Support timeline
Official dates from the PostgreSQL release process.
| Milestone | Date | Status |
|---|---|---|
| Initial release | 14 Sept 2023 | — |
| End of life (scheduled) | 9 Nov 2028 | in 823 days |
| Latest release | 16.14 · 11 May 2026 | current |
What you lose on 9 Nov 2028
Being supported means fixes keep shipping to this branch. Here is the stream that stops. Source: NVD.
PostgreSQL CVEs published and patched, by year
16 published in the last 12 months · data refreshed 2026-08-09
At the last-12-month rate of 16 PostgreSQL CVEs, running 16 for a year past 9 Nov 2028 means roughly that many vulnerabilities fixed upstream but never backported to your branch. Past branches bear this out: PostgreSQL 13 has missed 16 since it went end of life.
How much runway a newer branch buys
Moving to PostgreSQL 18 extends security support by about 735 days.
| Branch | End of life | Days left | vs 16 |
|---|---|---|---|
| PostgreSQL 18 | 14 Nov 2030 | 1,558 | +735 days |
| PostgreSQL 17 | 8 Nov 2029 | 1,187 | +364 days |
| PostgreSQL 16 | 9 Nov 2028 | 823 | this branch |
| PostgreSQL 15 | 11 Nov 2027 | 459 | -364 days |
| PostgreSQL 14 | 12 Nov 2026 | 95 | -728 days |
Review postgresql.org before moving to PostgreSQL 18.
Frequently asked questions
When does PostgreSQL 16 reach end of life?
PostgreSQL 16 reaches end of life on 9 Nov 2028 — 823 days from now. After that date it receives no security fixes.
Is PostgreSQL 16 still supported?
Yes. PostgreSQL 16 is currently maintained. Latest release: 16.14, published 11 May 2026.
What happens when PostgreSQL 16 reaches end of life?
Security fixes stop. Over the last 12 months 16 PostgreSQL vulnerabilities were published and patched across supported branches; once 16 is end of life, fixes at that rate no longer reach it.
How long do I have to upgrade from PostgreSQL 16?
823 days. Moving to PostgreSQL 18 instead buys roughly 735 more days of security support.