PostgreSQL 19 · Version Status

PostgreSQL 19 End of Life Date

PostgreSQL 19 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.

✓ PostgreSQL 19 is actively supported. EOL date: November 19, 2031.
📅 Get reminded before PostgreSQL 19 reaches EOL on November 19, 2031 — alerts 90, 30 & 7 days out.
Google →
✉️ Or get it by email — alerts at 90 / 60 / 30 / 7 days and on the day: Free · one-click unsubscribe in every email · no other mail, ever
Automating this check? GET https://api.endoflife.ai/v1/score/postgresql/19 returns this version's end-of-life date, its source and the EOL Risk Score as JSON. Get a free API key (150 requests a day, no expiry).
EOL Date
Nov 19, 2031
1826 days remaining
Latest Release
19.0
Standard release
Release Date
Nov 19, 2026
PostgreSQL 19 series
Where these dates come from
End of lifeNov 19, 2031Vendor's own page (our correction) · postgresql.org · checked Nov 19, 2026medium · 1 source agrees
ReleaseNov 19, 2026Vendor's own page (our correction) · postgresql.org · checked Nov 19, 2026medium · 1 source agrees
Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale. How we source dates.
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
Lifecycle detail

PostgreSQL 19 was released on November 19, 2026 and support is scheduled to end on November 19, 2031 — a planned supported lifespan of 5 years, in line with the 5 years and 1 month median for PostgreSQL releases. Its most recent patch is 19.0, published November 19, 2026.

← PostgreSQL 18 All PostgreSQL versions
30 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
Attack Surface
30/30 Critical tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
All PostgreSQL Versions
VersionLatestEOL DateStatus
6.0 6.0 Supported EOL
6.1 6.1.1 Supported EOL
6.2 6.2.1 Supported EOL
6.3 6.3.2 Mar 1, 2003 EOL
6.4 6.4.2 Oct 30, 2003 EOL
6.5 6.5.3 Jun 9, 2004 EOL
7.0 7.0.3 May 8, 2005 EOL
7.1 7.1.3 Apr 13, 2006 EOL

What does PostgreSQL 19 end of life mean?

When PostgreSQL 19 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running PostgreSQL 19 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to PostgreSQL 19 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does PostgreSQL 19 reach end of life?
PostgreSQL 19 reaches end of life on November 19, 2031. That is 1826 days remaining.
Is PostgreSQL 19 still supported?
Yes, PostgreSQL 19 is currently supported. The EOL date is November 19, 2031.
What should I upgrade to from PostgreSQL 19?
The recommended upgrade from PostgreSQL 19 is PostgreSQL 19 — the latest actively supported version. Check the PostgreSQL full timeline for all supported versions.
What are the security risks of running PostgreSQL 19 past EOL?
When PostgreSQL 19 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL PostgreSQL should migrate immediately or implement compensating controls.
Does PostgreSQL track end-of-life by point release (e.g. PostgreSQL 19.1, PostgreSQL 19.2)?
No — PostgreSQL end-of-life dates apply to the entire 19.x release series, not individual point releases. A point release like PostgreSQL 19.1 or PostgreSQL 19.2 shares the same EOL date as PostgreSQL 19. Security patches stop for the entire 19.x line on that date, regardless of which patch version you are running. Check the table above for EOL dates by major version series.
Deep Dive
Full guide
PostgreSQL End of Life & Support Options: What To Do When PostgreSQL Patches Stop (14 Ended November 12, 2026)
→
Version guide
PostgreSQL 14 Reached End of Life on November 12, 2026
→
Data from endoflife.date API · Generated at build time · How we source data →
Related Products
MySQLMariaDBPythonDjango