PostgreSQL 14 end of life
PostgreSQL 14 reaches end of life on 12 November 2026, five years after its release on 30 September 2021. Until then it receives quarterly minor releases on the community's February, May, August and November cadence. After that date the 14 line receives no further security, bug-fix or corruption fixes.
- End of life
- 12 November 2026
- Released
- Sept 2021
- Final release
- 14.24 (current)
- Successor
- PostgreSQL 17 or 18
Date published by PostgreSQL versioning policy. We do not publish a lifecycle date we cannot source.
What actually stops on 12 November 2026
- Quarterly minor releases on the 14 line, after the final November 2026 release.
- Security fixes and, equally important, fixes for data-corruption bugs.
- Community packaging updates for 14 on newer operating systems.
What actually breaks in the upgrade
The date shares a week with .NET 8 and .NET 9
12 November 2026 for PostgreSQL 14 and 10 November 2026 for .NET 8 and 9 land in the same week. Estates running both will have two unrelated upgrade programmes competing for the same change window and the same people. Plan them as one programme or one will slip.
Fourteen months is enough time, and it is the last comfortable window
Planning an upgrade now means an extension audit, a rehearsal, and a scheduled window. Planning it in October 2026 means an emergency. The difference in cost between the two is the entire argument for starting early.
Your options, costed honestly
Including the ones that do not involve buying anything from us.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Upgrade to 17 or 18 before November 2026 | Planned pg_upgrade with a rehearsal and a real window. | Days of work, weeks of calendar | Engineering time | Do this. The date is known and fourteen months is a comfortable runway. |
| Extended support on 14 from November 2026 | Backported fixes if the estate cannot move in time. | Days to onboard | Subscription | The fallback, not the plan. Worth arranging before the date rather than after. |
| Let the date pass | Unpatched from 13 November 2026. | None | Zero now | Avoidable. This is the one version line on this list where you still have time. |
What OSSeva does for PostgreSQL 14
OSSeva patches this line
OSSeva will backport security and corruption fixes to PostgreSQL 14 from the community end-of-life date. If you expect to still be on 14 in November 2026, the useful conversation is now, while an upgrade is still the cheaper option and we can tell you honestly which it should be.
PostgreSQL extended supportWhat your auditor will say
Nothing changes before the date. From 13 November 2026 requirement 6.3.3 applies the same way it does to any unsupported component.
Auditors increasingly ask for the lifecycle plan before the date rather than the remediation after it. A documented upgrade schedule is itself the evidence.
PostgreSQL 14: common questions
When does PostgreSQL 14 reach end of life?
12 November 2026, five years after its release on 30 September 2021. Until then it receives quarterly minor releases from the community.
Is PostgreSQL 14 still supported?
Yes, until 12 November 2026. It is in the community's quarterly minor release train until that date.
Should I upgrade PostgreSQL 13 to 14?
No. 14 reaches end of life on 12 November 2026, so it buys very little time. Go to 17 or 18 directly; pg_upgrade crosses multiple majors in a single step.
How long do I have to upgrade from PostgreSQL 14?
Until 12 November 2026. That is enough time to do an extension audit, rehearse the upgrade and schedule a real window, which is the difference between a planned change and an emergency one.
What happens to PostgreSQL 14 after November 2026?
The community publishes no further minor releases on the line. Security fixes and data-corruption fixes both stop. Third-party extended support becomes the only patch source.
Still running PostgreSQL 14?
Tell us the versions and the estate size. We will tell you honestly whether to upgrade or to buy cover — and we say 'upgrade' more often than you would expect.