Support for PostgreSQL 14 ended on November 12, 2026; on that date, version 14.25, the final update for this major release, was released. From now on, the PostgreSQL project will no longer fix new security vulnerabilities or bugs in version 14. The database is embedded in many systems that are not managed as database projects, such as traceability systems, test bench data, supplier portals, and warehouse management. Those affected include IT management, digitalization management, and application managers in manufacturing, intralogistics, and retail.
Databases with PostgreSQL 14 should first be updated to 14.25, then plan the move to 18, which receives updates until November 2030. Move your own applications with pg_upgrade in a maintenance window, vendor products once the vendor approves the new version. On Amazon RDS you have until February 28, 2027, after which Extended Support costs extra per vCPU and hour.
| Version | Last update according to PostgreSQL | Standard Support on Amazon RDS up to |
|---|---|---|
| PostgreSQL 14 | November 12, 2026 | February 28, 2027 |
| PostgreSQL 15 | November 11, 2027 | February 29, 2028 |
| PostgreSQL 16 | November 9, 2028 | February 28, 2029 |
| PostgreSQL 17 | November 8, 2029 | February 28, 2030 |
| PostgreSQL 18 | November 14, 2030 | February 28, 2031 |
What the End of Support for PostgreSQL 14 Means
The PostgreSQL project maintains each major version for five years. Version 14 was released on September 30, 2021, and its final update, 14.25, on November 12, 2026 (PostgreSQL Versioning Policy). The database will continue to run unchanged after that. If a new vulnerability is discovered, it will remain open in 14.
The latest update itself is worth noting. According to the release notes, version 14.25 fixes several bugs that can corrupt indexes and recommends rebuilding affected indexes (PostgreSQL 14.25 Release Notes). If you're switching over anyway, install 14.25 beforehand and check the indexes.
years is how long the PostgreSQL project maintains each major version, followed by exactly one final update.
PostgreSQL Versioning Policy, November 2026
A standard update is not sufficient to migrate to a new major version. You will need to use `pg_upgrade`, perform a dump followed by a restore, or use logical replication. Amazon RDS is extending standard support for version 14 through February 28, 2027. Starting March 1, 2027, AWS will charge for Extended Support for remaining instances on a per-vCPU, per-hour basis, in addition to the instance price, through February 28, 2030, at the latest (AWS RDS Release Calendar).
What this means for databases in manufacturing, warehousing, and retail
PostgreSQL is rarely run as a standalone project. It is often found in in-house developments, in vendor products with embedded databases, and in cloud instances that a project set up years ago. Most organizations do not have a complete list.
The jump from 14 to 18 introduces changes that require testing. Starting with version 18, initdb creates new clusters with data checksums, and pg_upgrade requires that the settings in the old and new clusters match (PostgreSQL 18 Release Notes). Starting with version 17, functions in expression indexes and materialized views must set their own search path when accessing other schemas (PostgreSQL 17 Release Notes). pg_upgrade does not handle logical replication slots until the old version is at least 17 (PostgreSQL Documentation on pg_upgrade).
A model calculation shows the order of magnitude. It assumes an automotive supplier with two plants and 18 instances running PostgreSQL 14: nine in-house applications, six vendor products and three instances on Amazon RDS with 4 vCPUs each. We estimate 3 to 5 person-days for the inventory and trial runs of pg_upgrade on copies. Each in-house application costs 1 to 3 person-days including tests, 9 to 27 in total. For the vendor products we assume half a day to one person-day each, so 3 to 6, and 1 to 2 each for the RDS instances, also 3 to 6. That adds up to 18 to 44 person-days. If the three RDS instances stayed on 14 for one year, an assumed rate of USD 0.100 per vCPU-hour, the example price for US East, would add around USD 10,500 for Extended Support, estimated as 12 vCPUs times 8,760 hours.
PostgreSQL Upgrade, Extended Support, or Wait and See: Your Options
| Option | Effort | Costs | Risk |
|---|---|---|---|
| Upgrade to 18 using pg_upgrade | 1 to 3 person-days per application with testing (estimate) | Internal Time | A maintenance window is required; clarify checksums and search paths beforehand |
| Upgrade to 17 if the vendor only approves 17 | As with 18 | Internal Time | Support ends on November 8, 2029, one year earlier than for version 18 |
| Migration via Logical Replication | 3 to 6 person-days per database (estimate) | Medium | Short switchover time; the existing replication from 14 must be reconfigured |
| Extended Support on Amazon RDS | None | From March 1, 2027, an extra charge per vCPU and hour, higher from the third year | Ends no later than February 28, 2030; this only postpones the date |
| Extended third-party support for self-hosted instances | Time required to switch packages | Recurring Fee | Temporary and dependent on the provider |
| Do nothing | None | None for now | New vulnerabilities remain open, audits lack a justification |
The vendor's instructions are authoritative. Test updates in a test environment first. How we migrate legacy systems during ongoing operations is described on the page Legacy Modernization with a Migration Plan.
Which path is right for which database?
In-house developments move directly to version 18 in a single step, following a test run on a copy of the production environment. We advise against using versions 15 and 16 as targets, because version 15 ends in November 2027, and the next project will follow immediately afterward.
For vendor products, the vendor's approval decides. Ask in writing for the supported version and date, and keep the database unreachable from the internet until then. On Amazon RDS, the upgrade belongs before February 28, 2027. Extended Support only pays off for systems with a fixed replacement date.
PostgreSQL Upgrade Plan in Five Business DaysWe record all PostgreSQL instances, including their version, size, extensions, application, and availability. On copies, we run pg_upgrade in test mode and check expression indexes, checksums, and replication. For each instance, you’ll receive the target version, migration path, maintenance window, and estimated effort. You can then decide which instances your team will migrate themselves, which ones to outsource, and which ones to bridge until they are replaced.
Frequently Asked Questions
How much does a PostgreSQL upgrade from version 14 to 18 cost?
In our model calculation, in-house development including testing takes 1 to 3 person-days. For 18 instances across two plants, this amounts to 18 to 44 person-days. The biggest differences stem from extensions, expression indexes, and the number of applications per database.
Is upgrading to PostgreSQL 15 or 16 enough?
Technically, yes; economically, rarely. PostgreSQL 15 will receive updates only through November 11, 2027, and version 16 through November 9, 2028. For the same amount of testing effort, version 18 will be supported through November 2030.
How long will PostgreSQL 14 Extended Support be available on Amazon RDS?
According to AWS, Standard Support for version 14 runs through February 28, 2027. After that, Extended Support is available through February 28, 2030, with the higher third-year prices taking effect on March 1, 2029.
The Next Step
torck modernizes legacy systems in industry and retail without interrupting operations, from the initial assessment through to the migration. You can find out how we do this on the page Legacy Modernization. For more background information, see Modernize or Replace Legacy Software, End of Support for Windows Server 2016 and .NET 8 End of Support. Schedule an Initial Consultation.