GetEndOfLife
Sign up
PostgreSQL

PostgreSQL

Database

PostgreSQL 18 is the newest actively maintained release, currently at patch 18.4. 5 of 29 tracked cycles remain supported. The next cycle scheduled to reach end-of-life is 14, on November 12, 2026.

Latest version

18.4

May 11, 2026

Actively maintained cycles

5

of 29 tracked

Total cycles tracked

29

since Mar 1, 1998

How PostgreSQL versioning, EOL & security support work

PostgreSQL does not use semantic versioning. Since version 10, the version number is major.minor (for example 17.6), where the first number is the major release and the second is a bug-fix-only minor release. The PostgreSQL Global Development Group ships a new major version about once a year, and each major version then receives minor releases on a regular cadence, at least once every three months, or sooner for urgent fixes. Minor releases never add features, only bug and security fixes.

Actively maintained

A major version is fully supported for five years from its initial release, keeping receiving regular minor releases with bug fixes, data-corruption fixes, and security patches.

Security support only (final release)

PostgreSQL doesn't define a separate extended or security-only tier the way some vendors do. As a major version's five-year window closes, the Global Development Group ships one last minor release bundling outstanding fixes, explicitly positioned as the final update before that major version leaves support.

End of life

Once the five years elapse, the major version is officially unsupported: no further bug fixes, security patches, or official builds, regardless of how widely it remains deployed.

PostgreSQL security issues are handled through a dedicated, private security process: reports go to the project's security team, are investigated confidentially, and a fix is coordinated for release, with advance notice so major packagers and cloud providers can prepare before it goes public. Each addressed issue is tracked with a CVE. Running a version past its five-year window means any new CVE affecting it will simply never be patched.

Sources: PostgreSQL Versioning Policy

Release lifecycle

Actively maintainedSecurity support onlyEnd of life
Today
18Latest
18.4 · May 11, 2026
17
17.10 · May 11, 2026
16
16.14 · May 11, 2026
15
15.18 · May 11, 2026
14
14.23 · May 11, 2026
13
EOL Nov 13, 2025
12
EOL Nov 21, 2024
11
EOL Nov 9, 2023
10
EOL Nov 10, 2022
9.6
EOL Nov 11, 2021
9.5
EOL Feb 11, 2021
9.4
EOL Feb 13, 2020
9.3
EOL Nov 8, 2018
9.2
EOL Nov 9, 2017
9.1
EOL Oct 27, 2016
9.0
EOL Oct 8, 2015
8.4
EOL Jul 24, 2014
8.3
EOL Feb 7, 2013
8.2
EOL Dec 5, 2011
8.1
EOL Nov 8, 2010
8.0
EOL Oct 1, 2010
7.4
EOL Oct 1, 2010
7.3
EOL Nov 27, 2007
7.2
EOL Feb 4, 2007
7.1
EOL Apr 13, 2006
7.0
EOL May 8, 2005
6.5
EOL Jun 9, 2004
6.4
EOL Oct 30, 2003
6.3
EOL Mar 1, 2003
19981999200020012002200320042005200620072008200920102011201220132014201520162017201820192020202120222023202420252026

Data sourced from endoflife.date.

Want to hear about it the moment PostgreSQL has a new release or reaches end-of-life?

Get alerts