Notes7 min read

PostgreSQL 14 in a deal: an unpatched database and a bill that grows by itself

PostgreSQL 14 received its final release on 12 November 2026, and on Amazon RDS and Aurora paid Extended Support starts on 1 March 2027. For a company sold or bought around that date, a database version becomes both a security finding and a new line in the cloud bill. What a buyer's reviewer reads, how it becomes a deal term, and what a seller can do now.

On 12 November 2026 the PostgreSQL project shipped 14.25, the final release of PostgreSQL 14. The project publishes no more fixes for it. On Amazon RDS and Aurora, AWS keeps 14 in standard support until 28 February 2027. From 1 March 2027 every database still on 14 moves into paid Extended Support, and the charge appears on the bill without anyone signing anything. Around a sale that is two findings at once: a database without fixes, and a cost line that grows on its own.

This note is for owners preparing a sale, buyers reading a target and their advisors. How to run the upgrade is an engineering question. Here we look at what the dates do to a deal.

The dates

WhenWhat happens
12 November 2026PostgreSQL 14.25, the final community release. Version 14 is end of life: no further security or bug fixes from the project.
Until 28 February 2027RDS for PostgreSQL 14 and Aurora PostgreSQL 14 stay in AWS standard support.
1 March 2027Extended Support charges start for RDS and Aurora databases still on 14, at the year 1 rate.
1 March 2029The year 3 rate starts, twice the earlier one.
28 February 2030Extended Support ends. AWS upgrades databases still on 14 automatically.

The community date comes from the PostgreSQL release announcement of 12 November 2026 and the project's versioning policy. The AWS dates come from the release calendars for RDS for PostgreSQL and Aurora PostgreSQL. We keep them, with other dates that matter to owners, on our page of technology deadlines for owners. To see which of them apply to your own software, drop your project files into our stack check; nothing leaves your browser.

A bill that grows by itself

AWS describes RDS Extended Support as a paid way to keep running a major version after standard support ends. Unless a database was set to opt out, AWS enrolls it automatically, and charges start the day after the end of standard support. For provisioned instances the price is per vCPU per hour. These are the rates AWS publishes for US East (N. Virginia) on the RDS for PostgreSQL and Aurora pricing pages, as of 18 November 2026:

EngineYears 1 and 2 (from 1 March 2027)Year 3 (from 1 March 2029)
RDS for PostgreSQL, provisioned$0.100 per vCPU-hour$0.200 per vCPU-hour
Aurora PostgreSQL, provisioned$0.100 per vCPU-hour$0.200 per vCPU-hour
Aurora Serverless v2$0.085 per ACU-hour$0.170 per ACU-hour

Three details make the line larger than it looks. The charge applies to the Multi-AZ standby and to every read replica on the old version, not only to the primary. Reserved Instance discounts do not apply. And a snapshot restored to a new instance on 14 after the date is charged too.

A hypothetical example. One production database on a db.r6g.xlarge instance (4 vCPU, as AWS lists it), Multi-AZ with one standby, in us-east-1. That is 8 vCPU billed. For a year counted as 8,760 hours: 8 × $0.100 × 8,760 = $7,008 a year in years 1 and 2, and 8 × $0.200 × 8,760 = $14,016 in year 3. For comparison, AWS lists that Multi-AZ instance on demand at $0.899 an hour, or 0.899 × 8,760 = about $7,875 a year. Here the support line costs nearly as much as the database it covers, then about twice as much. These are list prices for one region at the time of writing, not a quote.

What the money buys is limited: security updates for critical and high CVEs, fixes for critical bugs and support cases. It buys time. It does not move the database forward.

Why it reaches a deal

The first reason is security. A self-hosted PostgreSQL 14, on a cloud server, in containers or on the company's own hardware, now gets no fixes at all. A reviewer sees a core component past its end of life, usually the one that holds the customer data. Enterprise customers and insurers often ask whether any production software is out of support, and the honest answer changes.

The second is cost. A deal signed this winter and closed next spring crosses 1 March 2027. The bill in the data room may not show the new line; the buyer's first year will. A recurring cost that appears after the numbers were taken is a question about the run rate.

The third is that the work cannot be avoided, only moved. The rate doubles in 2029 and the version is upgraded automatically in 2030. AWS itself warns that major version upgrades can contain changes that are not backward compatible. An upgrade nobody tested, on a date nobody chose, is a real risk to the product. One more trap: turning off enrollment on a database already past the date does not stop the charge quietly. AWS upgrades that database to the next major version.

What a reviewer looks at

Most of this comes from the cloud console, the bill and the code in a day or two:

  • Every database and its version: production, staging, analytics copies and replicas, including self-hosted ones that never appear in the RDS console, with the minor version: the last 14 release has every fix the project shipped, an early one does not.
  • Aurora specifics: AWS lists Aurora PostgreSQL 14.6 (LTS) as the minor version eligible for Extended Support, with others to be determined.
  • The enrollment setting: for each instance and cluster, whether it will go into paid support or was set to opt out, which past the date means an automatic upgrade.
  • The cost: vCPU across primaries, standbys and replicas, times the rate, and whether it is in the budget the buyer receives.
  • What decides the size of the upgrade: the extensions in use (AWS notes that most are not upgraded with the engine), how much logic lives in the database itself, the application's drivers and frameworks, the size of the data, the downtime the business accepts, and whether there is a copy to test on.
  • The plan: a target version, a date, a test approach and a named person.

How a finding like this is rated, from Critical to Low, is set out in our severity scale.

How it turns into deal terms

On its own, a database version rarely moves a price. The charge is small next to the value of most companies, and an upgrade is planned work. It becomes a deal point when nobody can produce a list of databases, when customer data sits on a self-hosted 14 with no fixes, when the Extended Support cost is missing from the numbers, or when the upgrade is blocked by an extension or by old application code that nobody owns. Then the familiar mechanisms apply: an upgrade before closing as a condition, the cost of the upgrade and of support until then reflected in the price or held back, or a disclosure with the plan and the estimate. The choice is for the parties and their lawyers. The reviewer's job is to give them the list, the risk, the effort and the cost, with the assumptions written down. The assessment stays separate from the repair, which the company's team or a team it chooses does under its own scope.

What a seller can do now

  1. List every PostgreSQL database with its exact version, managed and self-hosted, with replicas and copies.
  2. Work out the charge from 1 March 2027 with your region's rate, and put it in the budget.
  3. Get an upgrade estimate: target version, extensions, tests, downtime window. Those decide the size, not the version number.
  4. Upgrade before 1 March 2027 if it fits. Test on a copy first. For RDS, AWS offers blue/green deployments, where the switch to the upgraded copy typically takes under a minute.
  5. If it does not fit, document it. The plan, the date, the budget, the owner and the support cost until then. Our note on the technical section of a data room shows where it goes.

This is the kind of item our exit readiness program tracks month by month.

What a buyer can do

Ask early for the list of databases and versions and the latest cloud bill by line item. Model the support cost until the upgrade is realistically done, not until the date in the plan. Decide early whether an upgrade before closing is a condition; it changes the deal timeline. If it is not finished at closing, put it in the first hundred days with an owner and a budget. A red-flag memo early in the process puts it on the table while it can still be priced.

A short checklist

  • Every PostgreSQL database listed with major and minor version, managed and self-hosted.
  • Extended Support enrollment checked for each instance and cluster.
  • The expected charge from 1 March 2027 calculated and in the budget.
  • An upgrade plan with a target version, a test approach, a date and an owner, or a dated reason to wait.
  • How the item is shown in the data room and in the disclosure.

Questions

Does our product stop working when PostgreSQL 14 reaches end of life?

No. The database runs the day after as it ran the day before. What changes is that the PostgreSQL project publishes no more security or bug fixes for version 14. On Amazon RDS and Aurora, AWS keeps it in standard support until 28 February 2027, and after that only paid Extended Support covers critical and high security issues and critical bugs.

How much does RDS Extended Support cost for PostgreSQL 14?

AWS prices it per vCPU per hour for provisioned instances. In US East (N. Virginia) the published rate is $0.100 per vCPU-hour from 1 March 2027 and $0.200 from 1 March 2029, for both RDS and Aurora PostgreSQL. Standbys and read replicas are charged too, and Reserved Instance discounts do not apply. Other regions have their own rates.

Can we just switch Extended Support off to avoid the charge?

Not without consequences. AWS states that if you disable enrollment on a database that is already past its end of standard support, the database is upgraded automatically to the next supported major version. Opting out before the date, with a tested upgrade, is the way to avoid the charge. Opting out after it means an upgrade on a date you did not plan.

Is a PostgreSQL 14 database a reason to lower the price?

Rarely on its own. The support charge is usually small next to the value of a company, and an upgrade is planned work. It becomes a deal point when nobody can list the databases, when customer data sits on an unpatched self-hosted 14, when the charge is missing from the numbers, or when an extension or old code blocks the upgrade.

Where are the dates for other technologies?

On our page of technology deadlines for owners, which lists end of support, major releases and new rules for languages, frameworks, databases and platforms, each with a link to its official source. The PostgreSQL 14 end of life and the Amazon RDS Extended Support date are both on it.

Written by
Yevhen Borovoi
FounderYevhen Borovoi

Founder of PERETZ, DeZZign, The Structure and NEX, partner at SCHOEFFEL. An engineer by training who reads a business as one system: strategy, product, technology, processes and economics.

Next step

Preparing a sale or looking at a target?

We reply within one business day. NDA before any documents change hands.