Back to blog

OSSeva Blog

Operations

How to Choose a PostgreSQL Extended Support Vendor

7 min read

How do you choose a PostgreSQL extended support vendor?

Check five things in this order: which versions the vendor covers, who writes the fix, how the fix reaches your servers, what evidence an auditor gets, and how you leave. A vendor that cannot answer the first one in writing, with minor version numbers, is not selling extended support for your version. If you can upgrade, upgrade first, and buy support only for the servers that cannot move.

This guide is for self-managed servers. If your database runs on a managed service, the cloud provider's own extended support applies instead; see what RDS Extended Support costs for PostgreSQL. For OSSeva's offer, see PostgreSQL end-of-life support.

Running PostgreSQL in production? OSSeva patches and supports it, end-of-life versions included.

PostgreSQL extended support: what is covered

Which questions separate extended support from ordinary support?

Ordinary support helps you run a version. Extended support ships new security fixes for a version the community has stopped fixing. Ask each vendor these seven questions and keep the answers in writing:

QuestionA good answerA weak answer
Which exact versions do you patch?A published list with minor numbers, for example 14.x from 14.25"All PostgreSQL versions" or a list that omits yours
Who writes the fix?The vendor backports the community fix to your major and tests itThe vendor advises you to patch it yourself
What about extensions?It names which extension fixes it carries and which stay with the extension's maintainerSilence, or a blanket promise
How fast are fixes?A published target by severity, such as Critical within 48 hours and High within 7 days"As soon as possible"
How does it reach my servers?Signed packages or images through your own repository, installed like a minor update on the same data directoryA new distribution that needs a migration
What evidence do I get?A record per CVE that names the fix, the affected versions and the buildA general statement that the product is "secure"
How do I leave?The builds keep running, and your packages and runbooks stay yoursLicence terms that stop the software when the contract ends

Which versions do the main providers cover?

Coverage differs more than most buyers expect. From each provider's own pages, read on 17 November 2026:

ProviderVersions past community end of lifeRuns where
OSSeva11, 12, 13 and 14Self-managed servers on any infrastructure
HeroDevs Never-Ending SupportLists 14.x, 16.x and 18.xLinux, Windows Server, Solaris and AIX builds
Amazon RDS and Aurora extended support11, 12 and 13 now; 14 from 1 March 2027Only on RDS and Aurora
Azure Database for PostgreSQL extended support11, 12 and 13 now; 14 from 1 February 2027Only on Azure
Google Cloud SQL extended support11, 12 and 13 now; 14 from 1 February 2027Only on Cloud SQL

HeroDevs lists 14, 16 and 18, so a server on 12 or 13 sits outside its published coverage. The cloud programmes patch nothing outside their own service. The comparison of PostgreSQL end-of-life support providers adds Canonical, EDB, Percona and OpenLogic, and says which of them sell patched builds and which sell support for current versions only.

When is a different provider the better fit?

Sometimes it is. HeroDevs publishes builds for Windows Server, AIX and Solaris and describes them as FIPS-capable. OSSeva ships DEB and RPM packages, tarballs and container images, so check the platform list first. If the database runs on RDS, Azure or Cloud SQL and has to stay there for another year or two, the provider's extended support is simpler than leaving the service. If the server runs the PostgreSQL package from Ubuntu's own repositories, check Canonical's Ubuntu Pro before you add a second vendor. And if the extensions have builds for 17 or 18, upgrading removes the need to buy anything.

Extended support fits best when an application vendor has not certified a newer major, when a regulated change freeze blocks the move, or when a large estate needs several quarters to finish. In each case, write down an upgrade date per cluster, so the support has an end.

What should the contract say?

  • The version list, with the first covered minor for each, and what happens when you upgrade a cluster out of coverage.
  • The fix targets by severity, and how the vendor tells you when a CVE affects your version.
  • The delivery route: which repository or image registry, who signs the builds, and how you verify them.
  • The extension boundary: which fixes the vendor carries and which stay with the maintainer.
  • Response times for incidents, if you buy operations cover. OSSeva Operate commits to a 15-minute response on P1, one hour on P2 and four hours on P3.
  • Exit terms: what keeps running, and which documents and packages you retain, if you end the contract. See PostgreSQL support without migration for the takeover and exit checklist.

How we compared

Provider facts above come from each provider's own documentation or pricing pages, read on 17 November 2026. We used no reviews or analyst rankings, and we show no prices because vendors quote them per estate. OSSeva sells one of the options listed, so check its row against the others.

Where does OSSeva fit?

OSSeva backports security and data-corruption fixes to self-managed PostgreSQL 11 to 14, ships them as signed packages and container images, and covers Patroni and repmgr clusters. Patch SLA: Critical within 48 hours, High within 7 days. Assure adds migration planning to 17 or 18, and Operate adds 24/7 monitoring. See PostgreSQL end-of-life support, PostgreSQL 14 end of life and PostgreSQL 13 end of life.

Frequently asked questions

What is PostgreSQL extended support?

Security and data-corruption fixes for a major version after the PostgreSQL project has stopped releasing them, supplied by a vendor or a cloud provider.

Is extended support a substitute for upgrading?

No. It buys time for servers that cannot move yet. Record an upgrade date for each one.

Can a vendor patch my PostgreSQL without a migration?

Yes, if it ships patched builds of the same major version. They install like a minor release on the same data directory. A vendor that needs a new distribution or a data move is selling a migration.

What should I ask a vendor before I sign?

The exact versions and minors covered, who writes the fix, how extension fixes are handled, the fix targets by severity, how builds are delivered and signed, and what keeps running if you leave.

Tags

PostgreSQLExtended SupportVendor ComparisonEnd of LifeBuyer's Guide

Get a quote

Ready to get your open source under control?

Tell us what you run. An OSSeva engineer replies within 1 business day with CVE coverage and a price for your stack.

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

Prefer to talk or read more first?

Book a call