In October 2026, which PostgreSQL major versions still receive minor releases, and what does end of life mean for a server still on PostgreSQL 13?
answer
- five years from the .0 release
- one last minor after the anniversary
- count back from the newest major
- fixes stop, the server keeps running
basics
~20 sEach PostgreSQL major gets minor releases for five years, then one final minor. In October 2026 that means 14 to 18, with 14's final minor due in November 2026. PostgreSQL 13 had its last minor in November 2025 and gets no more fixes.
solid answer
~40 sThe project supports a major for five years from its first release; after the fifth anniversary it ships one final minor and the branch is end of life. With a major every autumn, about five are supported at once: in October 2026 that is 14, 15, 16, 17 and 18, at 14.24, 15.19, 16.15, 17.11 and 18.6, and 14 gets its final minor in November 2026. PostgreSQL 13 had its last minor in November 2025. End of life switches nothing off: a 13 server keeps running and replicating. What stops is fixes: the CVE and data-corruption fixes back-patched to 14 to 18 since then were never released for 13, and tools gradually stop testing against it. The answer is a major upgrade, and going straight to 18 buys support until November 2030.
go deeper
Remember the five-year rule and that roughly five majors are supported at once; know which ones are current today.
Explain what end of life removes, fixes and ecosystem support, and how the quarterly schedule and out-of-cycle releases fit together.
Turn the policy into a schedule: find every server's major, map it to its final minor, and start upgrade projects early enough to finish before support ends.
Set a fleet policy, such as never running a major within a year of its end, and weigh fewer, larger jumps against more frequent, smaller ones.
## The support policy The PostgreSQL project supports each **major version** for **five years** after its initial release. During that time it ships **minor releases** for it: bug fixes and security fixes only. After the five-year anniversary the branch receives **one final minor release**, and then it is **end of life (EOL)**: no further releases of any kind. Two cadences drive the clock: - **Majors**: one a year, in the autumn. 17.0 shipped on 2024-09-26 and 18.0 on 2025-09-25. - **Minors**: scheduled once a quarter, on the second Thursday of February, May, August and November, for every supported major on the same day, plus **out-of-cycle** releases when a regression or an urgent security problem cannot wait for the next slot. The 18.x line shows both patterns: | Release | Date | Note | |---|---|---| | 18.0 | 2025-09-25 | The major release | | 18.1 | 2025-11-13 | Scheduled, November | | 18.2 | 2026-02-12 | Scheduled, February | | 18.3 | 2026-02-26 | Out of cycle, two weeks later, "a small number of fixes" | | 18.4 | 2026-05-14 | Scheduled, May | | 18.6 | 2026-08-13 | Scheduled, August; 18.5 was never released because of a regression found after it was wrapped | ## Which majors are supported in October 2026 Five-year support plus a yearly major means roughly five majors are alive at any moment. | Major | First released | Latest minor (Oct 2026) | Final minor expected | |---|---|---|---| | 18 | 2025 | 18.6 | November 2030 | | 17 | 2024 | 17.11 | November 2029 | | 16 | 2023 | 16.15 | November 2028 | | 15 | 2022 | 15.19 | November 2027 | | 14 | 2021 | 14.24 | November 2026 | | 13 | 2020 | none since November 2025 | End of life | The release notes show the cut-off. The fixes behind 18.6 went into 17.11, 16.15, 15.19 and 14.24 the same day, and nothing went to 13. November 2025 was the last batch that still included the 13 branch. ## What end of life means for a PostgreSQL 13 server End of life does **not** switch anything off. The server keeps starting, serving queries and streaming WAL to its standbys. What stops is everything around it: - **Security fixes stop.** Any vulnerability found since November 2025 that also affects 13 stays open there. The August 2026 batch alone carried several CVE fixes, back-patched to 14 and not to 13. - **Bug fixes stop**, including fixes for wrong results, crashes and index corruption, the kind whose notes ask you to reindex after updating. - **The ecosystem drifts away.** Extensions, backup tools and HA managers test against supported branches, and packagers stop producing new builds for it. - **Audits flag it.** Unsupported software is a standard finding in security reviews and compliance checks. Applying 13's final minor was the best a 13 server could do, but it is a snapshot: it contains the fixes known in November 2025 and nothing found afterwards. ## Planning against the clock 1. Read the running version on every server with `SHOW server_version_num`; a value below `140000` is an end-of-life major today, and one below `150000` will be after November 2026. 2. Map each major to its final-minor date. A major-upgrade project needs application testing against every intervening major's incompatibilities, so start well before the date, not at it. The upgrade route itself (`pg_upgrade`, dump and restore, or logical replication) belongs to major-version migration. 3. Jump as far as you can test: going from 13 to 18 buys support until November 2030, while going to 14 buys about a month. 4. Until the move, stay on the latest minor of the major you run. ## Misconceptions to avoid - **There is no LTS tier.** Every PostgreSQL major gets the same five years; no release is short-term. - **Minor releases follow a calendar**, not only security events, so a quarter without a CVE still brings a release. - **Support is per major, not per minor.** 18.0 and 18.6 end at the same time; staying on 18.0 just means missing four releases of fixes. - **A newer major does not end an older one early.** 19, still in beta in October 2026, will not shorten 14's, 15's or 18's windows; each keeps its own five years.
- When PostgreSQL fixes a bug in a minor release, does every supported major get the fix?Every supported major that has the bug, on the same day. The August 2026 security fixes shipped as 18.6, 17.11, 16.15, 15.19 and 14.24 together. A fix for code that exists only in a newer major goes only there: 18.6's fix for bogus `reltuples` after parallel GIN index builds applies to 18 alone, because parallel GIN builds are new in 18.
- Why not wait for PostgreSQL 14's final minor before planning the move off 14?Because the upgrade is a project, not a command: testing applications against the incompatibilities of every major between 14 and the target, rehearsing the chosen route, and scheduling the cutover take weeks. Starting at the final minor means running unsupported during that work. Plan it a year ahead and treat the final minor as a deadline already passed if you are still on it.
- Only some PostgreSQL majors are long-term support releases; the rest get a year or two.
- An end-of-life PostgreSQL server stops starting or refuses connections.
- Security fixes keep being back-patched to old majors such as 13 indefinitely.
- Minor releases only appear when a CVE is found, so there is no schedule.
- Once a server runs its branch's final minor it is fully patched for good.
Assumes October 2026 with PostgreSQL 18.6 current: majors 14 to 18 are supported until 14's final minor in November 2026.