PostgreSQL 17 end of life
PostgreSQL 17 is supported by the PostgreSQL Global Development Group until 8 November 2029, five years after its first release on 26 September 2024. The current minor release is 17.11, from 13 August 2026. Minor releases with security and bug fixes continue until the end date, after which the community stops patching 17. PostgreSQL 18 is supported until 14 November 2030.
- End of life
- 8 November 2029
- Released
- Sept 2024
- Final release
- 17.11 (current minor, 13 August 2026)
- Successor
- PostgreSQL 18
Date published by PostgreSQL versioning policy. We do not publish a lifecycle date we cannot source.
Last reviewed
What actually stops on 8 November 2029
- Minor releases on the 17.x line after 8 November 2029.
- Security fixes for the server, libpq and the bundled client tools.
- Fixes for data-corruption and crash bugs.
What actually breaks in the upgrade
17 is a destination today
With support to November 2029, 17 is a common target for estates leaving 13, 14 or 15. pg_upgrade supports upgrades from 9.2 and later, so older clusters can land on 17 in one step.
Logical slots and 17.11
17.11 added output_plugin_libraries, which by default allows only pgoutput and test_decoding. From 17 onwards, pg_upgrade --check fails if the new cluster does not permit the output plugins used by the old cluster's logical replication slots, so set it on the target before a later upgrade.
Moving on to 18
PostgreSQL 18 enables data checksums by default, and pg_upgrade needs matching settings, so a 17 cluster without checksums needs the new cluster initialised with --no-data-checksums. pg_upgrade in 18 keeps optimizer statistics across the upgrade.
Your options, costed honestly
Including the ones that do not involve buying anything from us.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Stay on 17 and take each minor | Community minor releases continue to 8 November 2029. | Hours per release | Engineering time | The right answer for most 17 clusters until 2028. |
| Upgrade to PostgreSQL 18 | One more year of runway, to November 2030. | Weeks | Engineering time | Worth it when a cluster is being rebuilt anyway. |
| OSSeva support on PostgreSQL 17 | Support and operations now, under one contract with the rest of the stack. | Days | Subscription | A good fit for estates consolidating several Postgres versions onto 17. |
What OSSeva does for PostgreSQL 17
OSSeva supports this line
PostgreSQL 17 is in OSSeva's PostgreSQL versions table as a current line and a recommended upgrade target. OSSeva supports it today, with fixes from the community's minor releases until 8 November 2029. Assure plans migrations onto 17 from older majors; Operate adds 24/7 replication and failover monitoring, including Patroni and repmgr, and point-in-time recovery testing.
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.
PostgreSQL 17: common questions
What is the PostgreSQL 17 end of life date?
8 November 2029, five years after its first release on 26 September 2024.
Is PostgreSQL 17 still supported?
Yes. The current minor release is 17.11, from 13 August 2026, and minor releases continue until 8 November 2029.
Should I upgrade to PostgreSQL 17 or 18?
Either is a sound target. 17 is supported until 8 November 2029 and 18 until 14 November 2030. 18 changes the checksum default, which matters for pg_upgrade from clusters created without checksums.
Can I upgrade from PostgreSQL 13 or 14 directly to 17?
Yes. pg_upgrade supports upgrades from 9.2 and later to the current major release in one step.
Still running PostgreSQL 17?
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.