PostgreSQL 6.4 End of Life
Support dates, vulnerabilities published since end of life, and upgrade guidance — rebuilt from live data.
PostgreSQL 6.4 reached end of life on 30 Oct 2003. It no longer receives security fixes.
Support timeline
Official dates from the PostgreSQL release process.
| Milestone | Date | Status |
|---|---|---|
| Initial release | 30 Oct 1998 | — |
| End of life | 30 Oct 2003 | 22.8 years ago |
| Latest release | 6.4.2 · 3 Jan 1999 | final |
The cost of staying: CVEs since end of life
169 PostgreSQL vulnerabilities have been published since 30 Oct 2003. All were fixed in supported branches — 6.4 received none of them. Source: NVD.
PostgreSQL CVEs published since 6.4's EOL, by year
7 of the 169 are rated critical · data refreshed 2026-08-09
Published 16 Aug 2017 · rated critical — fixed in supported branches only, never in 6.4. Details
Published 13 Nov 2018 · rated critical — fixed in supported branches only, never in 6.4. Details
Published 29 Oct 2019 · rated critical — fixed in supported branches only, never in 6.4. Details
Where to go from 6.4
Recommended target: PostgreSQL 18 (supported until 14 Nov 2030).
The newest actively supported branch is PostgreSQL 18 (latest release 18.4). Review postgresql.org before upgrading.
Frequently asked questions
Is PostgreSQL 6.4 still safe to use?
No. PostgreSQL 6.4 stopped receiving security fixes on 30 Oct 2003. Since then, 169 PostgreSQL vulnerabilities have been published and fixed in supported branches — PostgreSQL 6.4 received none of those fixes.
Can I still download PostgreSQL 6.4?
Yes — the final release (6.4.2) generally remains available from vendor archives and OS package mirrors, but installing it means running software with known, unpatched vulnerabilities.
What should I upgrade PostgreSQL 6.4 to?
Upgrade to PostgreSQL 18, the newest actively supported branch (supported until 14 Nov 2030).