PostgreSQL End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all PostgreSQL versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 6.3 | 6.3.2 | Mar 1, 1998 | Mar 1, 2003 | 8562 days past EOL | EOL |
| 6.4 | 6.4.2 | Oct 30, 1998 | Oct 30, 2003 | 8319 days past EOL | EOL |
| 6.5 | 6.5.3 | Jun 9, 1999 | Jun 9, 2004 | 8096 days past EOL | EOL |
| 7.0 | 7.0.3 | May 8, 2000 | May 8, 2005 | 7763 days past EOL | EOL |
| 7.1 | 7.1.3 | Apr 13, 2001 | Apr 13, 2006 | 7423 days past EOL | EOL |
| 7.2 | 7.2.8 | Feb 4, 2002 | Feb 4, 2007 | 7126 days past EOL | EOL |
| 7.3 | 7.3.21 | Nov 27, 2002 | Nov 27, 2007 | 6830 days past EOL | EOL |
| 7.4 | 7.4.30 | Nov 17, 2003 | Oct 1, 2010 | 5791 days past EOL | EOL |
| 8.0 | 8.0.26 | Jan 19, 2005 | Oct 1, 2010 | 5791 days past EOL | EOL |
| 8.1 | 8.1.23 | Nov 8, 2005 | Nov 8, 2010 | 5753 days past EOL | EOL |
| 8.2 | 8.2.23 | Dec 5, 2006 | Dec 5, 2011 | 5361 days past EOL | EOL |
| 8.3 | 8.3.23 | Feb 4, 2008 | Feb 7, 2013 | 4931 days past EOL | EOL |
| 8.4 | 8.4.22 | Jul 1, 2009 | Jul 24, 2014 | 4399 days past EOL | EOL |
| 9.0 | 9.0.23 | Sep 20, 2010 | Oct 8, 2015 | 3958 days past EOL | EOL |
| 9.1 | 9.1.24 | Sep 12, 2011 | Oct 27, 2016 | 3573 days past EOL | EOL |
| 9.2 | 9.2.24 | Sep 10, 2012 | Nov 9, 2017 | 3195 days past EOL | EOL |
| 9.3 | 9.3.25 | Sep 9, 2013 | Nov 8, 2018 | 2831 days past EOL | EOL |
| 9.4 | 9.4.26 | Dec 18, 2014 | Feb 13, 2020 | 2369 days past EOL | EOL |
| 9.5 | 9.5.25 | Jan 7, 2016 | Feb 11, 2021 | 2005 days past EOL | EOL |
| 9.6 | 9.6.24 | Sep 29, 2016 | Nov 11, 2021 | 1732 days past EOL | EOL |
| 10 | 10.23 | Oct 5, 2017 | Nov 10, 2022 | 1368 days past EOL | EOL |
| 11 | 11.22 | Oct 18, 2018 | Nov 9, 2023 | 1004 days past EOL | EOL |
| 12 | 12.22 | Oct 3, 2019 | Nov 21, 2024 | 626 days past EOL | EOL |
| 13 | 13.23 | Sep 24, 2020 | Nov 13, 2025 | 269 days past EOL | EOL |
| 14 | 14.23 | Sep 30, 2021 | Nov 12, 2026 | 95 days remaining | Warning |
| 15 | 15.18 | Oct 13, 2022 | Nov 11, 2027 | 459 days remaining | Active |
| 16 | 16.14 | Sep 14, 2023 | Nov 9, 2028 | 823 days remaining | Active |
| 17 | 17.10 | Sep 26, 2024 | Nov 8, 2029 | 1187 days remaining | Active |
| 18 | 18.4 | Sep 25, 2025 | Nov 14, 2030 | 1558 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/postgresql)
What does PostgreSQL end of life mean for your organization?
When a version of PostgreSQL reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL PostgreSQL should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when PostgreSQL reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in 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 purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL PostgreSQL versions. This is a bridge, not a permanent solution — plan your migration in parallel.
PostgreSQL has 24 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for PostgreSQL exists — vetted vendors ship security patches for years past the official date. Right now that coverage spans PostgreSQL 12.x, 13.x, 14.x. Tell us where to reach you and we'll reply with matched options and pricing guidance.