Who Provides PostgreSQL Support After End of Life? (PostgreSQL 12, 13 and 14)

The short answer

If your PostgreSQL runs on a managed service, the cloud provider extends it: Amazon RDS and Aurora Extended Support, Azure Database for PostgreSQL extended support and Cloud SQL extended support all patch critical and high CVEs for up to three years past standard support, for an extra charge. If you run PostgreSQL yourself, three providers publish patched builds for end-of-life versions: OSSeva (11, 12, 13, and 14 from 12 November 2026), HeroDevs (14, among the versions it lists) and Canonical (the PostgreSQL package each Ubuntu LTS ships, through Ubuntu Pro).

EDB, Percona and Perforce OpenLogic all sell PostgreSQL support, but none of them publishes patched community builds for a version after its end-of-life date. That distinction, between help running a version and new security fixes for it, is the one to check in any quote.

PostgreSQL end-of-life dates

The PostgreSQL Global Development Group supports each major version for five years, releases one final minor version, and then stops. After that date, community advisories list fixed versions for the supported branches only. The PostgreSQL end-of-life chart tracks every line, and PostgreSQL vulnerabilities by version shows which CVEs already reach the retired ones.

PostgreSQL end-of-life support providers compared

Each row reflects what the vendor publishes on its own site as of 6 October 2026.

Two rows are easy to misread. HeroDevs lists 14, 16 and 18, so a server on 12 or 13 is outside its published coverage. Canonical maintains the package Ubuntu ships, which means PostgreSQL 12 on Ubuntu 20.04 is covered while PostgreSQL 13 from the PGDG apt repository on the same machine is not.

How the providers differ

The cloud providers

AWS, Microsoft and Google all built the same mechanism: when a major version leaves the provider's standard support, the database is enrolled automatically, keeps running on the same engine, and is billed an extra charge until you upgrade. All three cap it at about three years, and AWS and Google upgrade the engine automatically when the window closes. On RDS, turning Extended Support off on a database already past its standard support date triggers a major-version upgrade straight away. AWS has published RDS-built minor versions for retired majors, such as 12.22-rds.20260514 and 13.23-rds.20260514, released on 29 September 2026. None of these patches reaches PostgreSQL outside the provider's managed service.

OSSeva

OSSeva for PostgreSQL backports security and data-corruption fixes from the supported branches into 11, 12 and 13 today, and into 14 once its final community release ships on 12 November 2026. A patched build stays on the same major version, so it installs like a minor release on the same data directory, and under Patroni it rolls through replicas first, then a switchover. Extensions such as PostGIS, pgvector and TimescaleDB are tested for compatibility against each build; security fixes inside third-party extension code stay with those projects. Assure adds major-version migration planning to 17 or 18, a vacuum and configuration audit and compliance attestations; Operate adds 24/7 replication and failover monitoring with a 15-minute P1 response.

HeroDevs

HeroDevs has the widest published platform matrix of the self-managed options, including Windows Server, AIX and Solaris, and offers FIPS 140-3 capable builds. Its published versions are 14, 16 and 18. See OSSeva vs HeroDevs for the wider overlap.

Canonical

If your PostgreSQL comes from Ubuntu's own packages, Ubuntu Pro is the lowest-friction option: fixes arrive through apt, and Canonical's PostgreSQL offer covers more than 40 extensions as well as the server. Ubuntu 20.04 ships PostgreSQL 12 in its main repository, and Ubuntu Pro covers 20.04 until May 2030. The limit is that you get the version your Ubuntu release ships, on Ubuntu.

EDB, Percona and OpenLogic

All three are strong choices for support on current versions. EDB sells its own EDB Postgres Advanced Server and Extended Server alongside support for community PostgreSQL; its published standard support for 14.x ends on 1 December 2026, and its managed Cloud Service offers Extended Life Support for retired versions to customers who buy it before the forced upgrade. Percona's lifecycle policy says end-of-life products get no bug fixes, new builds or packages, and its paid post-EOL contracts are for MySQL 5.7 and 8.0. OpenLogic supports PostgreSQL among 400-plus technologies, and its patched long-term support list covers other products. Our OSSeva vs Percona and OSSeva vs OpenLogic comparisons go further.

What is cheaper than Amazon RDS Extended Support for PostgreSQL?

Usually, a major-version upgrade inside RDS. How the charge is built explains the cheaper options:

• It is billed per vCPU per hour on provisioned instances, Multi-AZ standbys included, and per ACU per hour on Aurora Serverless.
• The rate rises in year 3. For PostgreSQL 14, year 1 pricing starts on 1 March 2027 and year 3 pricing on 1 March 2029.
• It stops as soon as the database runs a major version in standard support, or is deleted.

The alternatives, roughly in order of how often they come out cheaper:

1. Upgrade before the charge starts. RDS 14 stays in standard support until 28 February 2027, so a move to 17 or 18 before then avoids the premium entirely. Our PostgreSQL 14 upgrade guide covers the upgrade methods step by step.
2. Upgrade during year 1 or 2. If a database cannot move in time, pay the lower rate for as short a period as possible and finish before year 3 pricing.
3. Run PostgreSQL yourself with a support subscription. This fits when the database already runs, or could run, on EC2, Kubernetes or your own hardware, or when an application pins the version for years. OSSeva prices per cluster rather than per vCPU, so the bill does not rise with instance size. You take on backups, failover and patching, so compare the whole cost, not only the support line.

Moving a healthy RDS database off the service only to avoid the premium is rarely worth it. Our RDS Extended Support cost breakdown works through the dates with an example, and OSSeva vs RDS Extended Support sets out when each one fits.

Should you upgrade PostgreSQL or buy extended support?

Upgrade wherever you can do it safely; buy time for the clusters you cannot move before their date. Most estates do both, cluster by cluster.

pg_upgrade crosses several major versions in one step, so a server on 12 can go straight to 17 or 18. The major version upgrade guide covers the methods and rollback.

Where OSSeva fits

OSSeva covers self-managed PostgreSQL 11 to 14 past community end of life, delivered as signed packages and images through your own repositories, with Patroni and repmgr clusters supported. See PostgreSQL end-of-life support for the offer and the extended support vendor roundup for how OSSeva compares across other technologies.

Frequently asked questions

What are the best PostgreSQL end-of-life support providers?

It depends on where the database runs. On managed services, AWS, Azure and Google Cloud each extend retired versions for about three years. For self-managed servers, OSSeva patches 11 to 14, HeroDevs lists 14, 16 and 18, and Canonical patches the version Ubuntu ships. EDB, Percona and OpenLogic sell support for current versions.

Who supports PostgreSQL 14 after its November 2026 end of life?

On managed services: RDS and Aurora (standard support to 28 February 2027, then Extended Support to 28 February 2030), Azure (extended support from 1 February 2027 to 11 November 2029) and Cloud SQL (extended support from 1 February 2027). For self-managed servers: OSSeva, HeroDevs, and Canonical for the PostgreSQL 14 package in Ubuntu 22.04.

Who provides patched PostgreSQL 13 for self-managed servers?

OSSeva publishes patched builds of PostgreSQL 13, along with 11, 12 and 14. HeroDevs does not list 13, Ubuntu's LTS releases do not ship it, and Percona and EDB follow the community end-of-life date. On RDS, Azure and Cloud SQL, 13 is covered by each service's extended support.

Can I get PostgreSQL security patches after end of life?

Not from the PostgreSQL project, which states that no further security patches are made for end-of-life versions. They come from your cloud provider's extended support, from Canonical for Ubuntu's packages, or from a vendor that backports fixes, such as OSSeva or HeroDevs.

What is cheaper than Amazon RDS Extended Support for PostgreSQL?

Upgrading to a version in RDS standard support removes the charge entirely, and doing it before year 3 pricing limits the cost if you are already enrolled. Self-managed PostgreSQL with a per-cluster support subscription can cost less where the database can live outside RDS, once hosting and operations are counted.

Should we upgrade PostgreSQL or buy extended support?

Upgrade the clusters that can move to 17 or 18 safely. Buy extended support for those blocked by vendor certification, extension compatibility or the size of the estate, with an upgrade date recorded for each.