PostgreSQL 16 end of life
PostgreSQL 16 end of life is 9 November 2028. The PostgreSQL Global Development Group released 16 on 14 September 2023 and supports each major version for five years. The current minor release is 16.16, from 12 November 2026. PostgreSQL 14 ended first, on 12 November 2026 with 14.25, and 15 follows on 11 November 2027.
What now
Who provides PostgreSQL 16 security patches once community support ends?
PostgreSQL 14 extended support after 12 November 2026- End of life
- 9 November 2028
- Released
- Sept 2023
- Final release
- 16.16 (current minor, 12 November 2026)
- Successor
- PostgreSQL 17 or 18
Date published by PostgreSQL versioning policy. We do not publish a lifecycle date we cannot source. Dates checked on postgresql.org and endoflife.date on 22 October 2026.
Last reviewed
What actually stops on 9 November 2028
- Minor releases on the 16.x line after 9 November 2028.
- Security fixes for the server, libpq and the bundled client tools.
- Fixes for data-corruption and crash bugs, which make up much of each minor release.
What actually breaks in the upgrade
Read the 16.15 notes before updating
16.15 fixed CVE-2026-6471 by adding output_plugin_libraries, which limits logical decoding to listed output plugins. By default only pgoutput and test_decoding are allowed, so change data capture that relies on another plugin stops until you add it. The notes also ask users of btree_gist or ltree to check whether indexes need rebuilding.
Pick the target by its date
The community supports PostgreSQL 17 until 8 November 2029 and 18 until 14 November 2030. A move from 16 to 17 buys one year; a move to 18 buys two.
PostgreSQL 18 turns checksums on by default
initdb in PostgreSQL 18 enables data checksums by default, and pg_upgrade requires matching checksum settings. A 16 cluster created without checksums needs the new cluster initialised with --no-data-checksums. pg_upgrade in 18 also keeps optimizer statistics across the upgrade.
PostgreSQL 16 release date and the 14 to 18 end-of-life dates
PostgreSQL 16 sits in the middle of the five supported major versions. The table gives each version's first release date and its final release date, which is the end of community support. PostgreSQL 14 is the next to end, on 12 November 2026.
PostgreSQL 14 to 18: release dates, end-of-life dates and current minor
| Version | First release | End of life (final release) | Current minor |
|---|---|---|---|
| 18 | 25 Sep 2025 | 14 Nov 2030 | 18.7 |
| 17 | 26 Sep 2024 | 8 Nov 2029 | 17.12 |
| 16 | 14 Sep 2023 | 9 Nov 2028 | 16.16 |
| 15 | 13 Oct 2022 | 11 Nov 2027 | 15.20 |
| 14 | 30 Sep 2021 | 12 Nov 2026 | 14.25 |
Source: the PostgreSQL versioning policy, checked 12 November 2026. 14.25 is the final PostgreSQL 14 release.
CVEs fixed on PostgreSQL 16 in 2026
The 2026 minor releases fixed 81 CVEs that list PostgreSQL 16 as affected, and PostgreSQL scored 56 of them 7.0 or higher. Every one is fixed in the 16.x minor listed below, so a 16 server on its current minor has them all. A server that stops taking minors does not, which is what happens to every line when it ends.
2026 PostgreSQL security fixes that list 16 as affected
| Released | Fixed in 16 | CVEs fixed | Scored 7.0 or higher |
|---|---|---|---|
| 12 February 2026 | 16.12 | 4 | 3 |
| 14 May 2026 | 16.14 | 9 | 5 |
| 13 August 2026 | 16.15 | 25 | 16 |
| 12 November 2026 | 16.16 | 43 | 32 |
Source: the CVE table on postgresql.org/support/security, recounted on 17 November 2026. Scores are PostgreSQL's own as the CNA.
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 PostgreSQL 18 | pg_upgrade or logical replication to the newest major. | Depends on extension count, rehearsal time and downtime window | Engineering time | The longest runway, to November 2030. |
| Stay on 16 and take each minor | Community minor releases continue to 9 November 2028. | Hours per release | Engineering time | Fine for now. Apply the configuration changes each minor asks for. |
| OSSeva support on PostgreSQL 16 | Support and operations now, under one contract with the rest of the stack. | Days | Subscription | Puts the clusters under one supplier well before the date. |
What OSSeva does for PostgreSQL 16
OSSeva supports this line
PostgreSQL 16 is in OSSeva's PostgreSQL versions table as a current line, and OSSeva supports it today, with fixes from the community's minor releases until 9 November 2028. Assure adds major-version migration planning to 17 or 18; Operate adds 24/7 replication and failover monitoring, including Patroni and repmgr. OSSeva's patched builds cover 11, 12 and 13 today, and 14 from 12 November 2026.
PostgreSQL extended supportWhat your auditor will say
The data store is a system component in its own right. An unsupported version with no patch source is a finding; a documented third-party patch stream is the usual remediation.
Auditors ask for evidence that production systems receive security fixes. A version past end of life fails that test unless another supplier ships the fixes and can show which CVEs they close.
For EU financial entities, the ICT risk and third-party provisions apply when a critical service depends on software with no support arrangement in place.
What is the PostgreSQL 16 end of life date?
9 November 2028, five years after its first release on 14 September 2023.
Is PostgreSQL 16 still supported?
Yes. The current minor release is 16.16, from 12 November 2026, and minor releases continue until 9 November 2028.
What should I upgrade PostgreSQL 16 to?
17 or 18. PostgreSQL 17 is supported until 8 November 2029 and 18 until 14 November 2030. pg_upgrade crosses several major versions in one step.
What changed in PostgreSQL 16.15?
Among other fixes, a new output_plugin_libraries setting limits which logical decoding plugins replication users can load. Plugins other than pgoutput and test_decoding must be added to it after updating.
Get a quote
Still running PostgreSQL 16?
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.
Prefer to talk or read more first?