PostgreSQL 14 died today, November 12, 2026, at the age of five years and six weeks. Its last words were 14.25.
The release note is short about it: "This is the final release of PostgreSQL 14." (PostgreSQL news, Nov 12, 2026)
The record
| Born | September 30, 2021 |
| Died | November 12, 2026, with release 14.25 |
| Cause | the five-year support policy, as scheduled since birth |
| Survived by | about 89,500 files on GitHub that say image: postgres:14
|
| Replaced by | PostgreSQL 18, supported until November 14, 2030 |
Dates are from the PostgreSQL versioning page, read November 12, 2026. The file count is GitHub's code search for the exact string image: postgres:14, read November 11, 2026. It is approximate and includes forks, docs and examples.
What it did on its last day
It went out fixing things. Today's update release, 14.25 among them, closes a list of security issues; the release note gives each one with the versions it affects. Anything found after today stays open on 14.
What it leaves behind
Nothing stops. A server on 14 starts tomorrow the same way it started today. That is the trouble with this kind of death: there is no error to notice, only fixes that never arrive.
The heirs were named years ago. 15, 16, 17 and 18 are all supported, and pg_upgrade goes from 14 to 18 in one step.
On Amazon RDS, standard support for 14 runs until February 28, 2027, then paid Extended Support (AWS release calendar).
In lieu of flowers, check your compose files:
git grep -n "postgres:14"
What is the oldest PostgreSQL version you still have running somewhere, and what is keeping it there?
I'm Nabil. I build Since, which tracks what your code depends on and tells you before it breaks.
Top comments (0)