End of life

PostgreSQL 11 end of life

PostgreSQL 11 reached end of life on 9 November 2023 with the final release, 11.22. The PostgreSQL Global Development Group supports each major version for five years, so 11 no longer receives security or bug fixes. Managed services such as Amazon RDS now charge Extended Support fees to keep running it.

What now

Which vendors provide PostgreSQL 11 security patches now that support has ended?

PostgreSQL 14 extended support after 12 November 2026

Only your email is required · An engineer replies within 1 business day · No commitment

End of life
9 November 2023
Released
Oct 2018
Final release
11.22
Successor
PostgreSQL 17 or 18

Date published by PostgreSQL versioning policy. We do not publish a lifecycle date we cannot source. Dates checked on endoflife.date and postgresql.org on 20 October 2026.

Last reviewed

PostgreSQL versions: release and end-of-life dates

PostgreSQL release and end-of-life dates
VersionReleasedEnd of lifeStatus
PostgreSQL 1726 Sept 20248 November 2029Supported
PostgreSQL 1614 Sept 20239 November 2028Supported
PostgreSQL 1513 Oct 202211 November 2027Approaching
PostgreSQL 1430 Sept 202112 November 2026End of life
PostgreSQL 1324 Sept 202013 November 2025End of life
PostgreSQL 123 Oct 201921 November 2024End of life
PostgreSQL 11 (this page)18 Oct 20189 November 2023End of life

End-of-life dates are published by each project and checked against endoflife.date.

What actually stops on 9 November 2023

  • Minor releases on the 11.x line. 11.22 was the last.
  • Security fixes for the server, the bundled contrib modules and the client libraries shipped with it.
  • Packaging updates from the PGDG apt and yum repositories for new operating system releases.

What actually breaks in the upgrade

Extensions decide the upgrade

pg_upgrade itself is reliable. What blocks PostgreSQL 11 upgrades is usually an extension, such as PostGIS or TimescaleDB, that has to be upgraded in step, or an application that depends on behaviour a later version changed.

Skipping versions is normal

pg_upgrade moves directly from 11 to a current major version. There is no need to stop at 12, 13 and 14, which is one reason to plan the jump to a version with years of support left.

CVEs fixed since PostgreSQL 11 ended

PostgreSQL 11 ended on 9 November 2023 with 11.22, so all four 2026 minor-release sets came after it. They fixed 96 CVEs, and PostgreSQL scored 66 of them 7.0 or higher. None of those fixes has a release for 11. The project's advisories list versions 14 to 18 as affected, so 11 was not assessed. That is not a finding that it is safe.

2026 PostgreSQL security fixes and what 11 received

ReleasedFixed in supported linesCVEs fixedScored 7.0 or higherFix for 11
12 February 202618.2 to 14.2154No release
14 May 202618.4 to 14.23116No release
13 August 202618.6 to 14.242818No release
12 November 202618.7 to 14.255238No release

Source: the CVE table on postgresql.org/support/security, counted on 14 November 2026. Scores are PostgreSQL's own as the CNA. Counts cover 2026 only; fixes published between 9 November 2023 and the end of 2025 are not included.

Your options, costed honestly

Including the ones that do not involve buying anything from us.

OptionWhat it isEffortCostOur view
Upgrade to a current major versionpg_upgrade or logical replication to 17 or 18.Depends on extension count, rehearsal time and downtime windowEngineering timeThe destination for almost everyone.
Amazon RDS Extended SupportAWS keeps patching RDS PostgreSQL 11; it has been on the higher year-three rate since 1 April 2026.NoneBilled per vCPU-hour on top of the instance price; AWS publishes the rateConvenient inside RDS, and expensive for large instances.
Third-party extended supportBackported fixes for self-managed PostgreSQL 11.DaysSubscriptionFor self-managed servers pinned by an application or extension.

What OSSeva does for PostgreSQL 11

OSSeva patches this line

OSSeva backports security fixes to self-managed PostgreSQL 11 to 14 and supports the major version upgrade, including extension sequencing.

PostgreSQL extended support

What your auditor will say

PCI DSS 4.0

Requirement 6.3.3. A database holding cardholder data on an unsupported major version is a finding without a documented compensating control.

SOC 2

CC7.1. Auditors ask for evidence that production databases receive security fixes.

Compliance library PostgreSQL end of life dates for every version

Questions

PostgreSQL 11: common questions

Book a 15-minute call

When did PostgreSQL 11 reach end of life?

On 9 November 2023, with the release of 11.22.

How much does RDS Extended Support for PostgreSQL 11 cost?

AWS bills Extended Support per vCPU-hour on top of the instance price, and the rate rises in year three, which PostgreSQL 11 has been in since 1 April 2026. AWS publishes the rate on its RDS pricing page, and the charge scales with the vCPU count of each instance.

Can I upgrade PostgreSQL 11 straight to 17?

Yes. pg_upgrade supports upgrading directly across several major versions. Test extensions and application queries first.

Get a quote

Still running PostgreSQL 11?

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.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call