PostgreSQL 14 End of Life: Supabase, RDS and Neon Dates

PostgreSQL 14 End of Life: Supabase, RDS and Neon Dates

Executive Summary & Key Takeaways

PostgreSQL 14 reached community end of life on 12 November 2026. Your database keeps running, but community fixes stop, and each host sets its own dates. The PostgreSQL project's versioning page lists that date as the final release date for version 14, with 14.25 as the current minor release. If you run Postgres through Supabase, Amazon Relational Database Service (RDS) or Neon, your host has its own rules, and they differ.

Table of Contents
  1. What does end of life mean for Postgres 14?
  2. What does Supabase say about Postgres 14?
  3. What does AWS RDS say about Postgres 14?
  4. What does Neon say about Postgres 14?
  5. How do you upgrade safely? (general advice)
  6. What to do this week
  7. When you can skip this
  8. Need help with an old project?
  9. Common questions
  10. Sources

PostgreSQL 14 reached community end of life on 12 November 2026. Your database keeps running, but community fixes stop, and each host sets its own dates. The PostgreSQL project's versioning page lists that date as the final release date for version 14, with 14.25 as the current minor release. If you run Postgres through Supabase, Amazon Relational Database Service (RDS) or Neon, your host has its own rules, and they differ.

What does end of life mean for Postgres 14?

The PostgreSQL Global Development Group says it supports a major version for 5 years after its initial release. Version 14 first released on 30 September 2021. The versioning page lists 12 November 2026 as its final release. We read that as no more community minor releases for 14, which is where bug and security fixes ship. That is our reading, not a quote from the page. Your database keeps running. What stops is the flow of community fixes.

For reference, the same page lists final release dates of 11 November 2027 for version 15, 9 November 2028 for 16, 8 November 2029 for 17 and 14 November 2030 for 18.

What does Supabase say about Postgres 14?

Supabase has the earliest date of the three. Its deprecation notice, published 12 May 2026, says support for Postgres 14 is deprecated as of 1 July 2026. Per the notice, projects still on 14 on that date are upgraded automatically to the latest Postgres version available, and projects using unsupported extensions are paused and stop serving traffic. The notice says organisation owners with active Postgres 14 projects would get emails.

Supabase's upgrade docs name the extensions deprecated in Postgres 17: plcoffee, plls, plv8, timescaledb and pgjwt. They must be disabled before a move from 15 to 17. We found no later Supabase notice saying what happened to individual projects after 1 July, so open your dashboard and check the Postgres version yourself. The docs say your current service versions are in the dashboard's general settings.

The upgrade docs also describe how an upgrade works:

  • It is not a true in-place upgrade. A new instance is created and your data is copied to it and upgraded using pg_upgrade.
  • The project goes offline, so plan for the database and related services to be unavailable. The changelog notice says small databases take about 15 minutes and larger ones an hour or more.
  • Projects with read replicas cannot be upgraded. Logical replication slots must be dropped. Deprecated or unsupported extensions must be dropped.
  • The notice suggests testing your application on a new Postgres 17 project and listing extensions with SELECT * FROM pg_extension; before you start.

What does AWS RDS say about Postgres 14?

AWS publishes a release calendar for RDS for PostgreSQL. For major version 14 it lists:

  • Community end of life: 12 November 2026.
  • RDS end of standard support: 28 February 2027.
  • RDS Extended Support year 1 pricing starts 1 March 2027, and year 3 pricing starts 1 March 2029.
  • RDS end of Extended Support: 28 February 2030.

AWS says that if you have not upgraded by the end of standard support date, RDS automatically enrolls your databases in Extended Support, for a fee. AWS's pricing page gives Extended Support rates per vCPU-hour, and its examples show a higher rate from year 3, so we give no prices. AWS also says you can see support dates for your engine versions with the describe-db-major-engine-versions AWS CLI command.

What does Neon say about Postgres 14?

Neon's version policy page says Neon currently supports Postgres 14, 15, 16, 17 and 18, and that it supports the five latest major versions. It says 14.25 became available on Neon on 12 November 2026. The page gives no end-of-life date for 14 on Neon. For a major upgrade it says you create a new Neon project and migrate your data, and it links to its own upgrade guide, which we did not read.

How do you upgrade safely? (general advice)

These steps are general engineering practice, not taken from the host pages above.

  • Take a backup and test the restore. A backup you have never restored is a guess. See our post on testing a backup restore for an AI-built app.
  • Restore the backup to a copy and upgrade the copy first. Run your app against it.
  • List your extensions with SELECT extname, extversion FROM pg_extension; and compare them with your host's list of unsupported extensions.
  • Read the release notes for every major version between yours and your target. Supabase's docs say the same for projects on much older versions.
  • After the upgrade, run your tests, then check access rules as an anonymous user and as a normal user. Confirm that access rules still behave as before. Our post on Supabase RLS that is on but still exposes data shows what to test.
  • Freeze schema changes during the window and decide your rollback before you start. For most small teams, rollback means restoring the backup. See safe Postgres migrations for small teams.

On the target version: Supabase's docs and notice talk about moving to 17, RDS lists 15 to 18 in its calendar, and Neon lists up to 18. Pick a version your host supports and your extensions support. We did not check PostgreSQL 19 on any host.

What to do this week

  • Find out which Postgres version every project and environment runs, including staging and old client projects.
  • On Supabase, check the version in the dashboard. On RDS, check the engine version and note 28 February 2027. On Neon, check the project's Postgres version.
  • On Supabase, also check the API keys deprecation: what to migrate and rotate.
  • List extensions on each database.
  • Confirm you have a recent backup and have restored it at least once.
  • Book a maintenance window and a test run on a copy.

When you can skip this

Skip this if every database you run is already on Postgres 15 or later. Skip the RDS section if you are not on RDS, and the Neon section if you are not on Neon. If you are on Supabase and your dashboard already shows a newer version, you are done, apart from a backup check.

Need help with an old project?

Older projects, especially ones handed over without notes, often have a database nobody has looked at in a while. A code and health review can list the Postgres version, extensions and backup state before you plan the upgrade. You can start with the free code review or talk to us about Launch and Rescue.

Common questions

Is PostgreSQL 14 still supported?

Not by the community. The PostgreSQL versioning page lists 12 November 2026 as the final release date for 14. Hosts set their own dates: AWS lists 28 February 2027 for the end of RDS standard support, and Supabase's notice says Postgres 14 support was deprecated from 1 July 2026.

What happens to a Supabase project still on Postgres 14?

Per Supabase's deprecation notice, it is upgraded automatically to the latest available Postgres version, unless it uses unsupported extensions, in which case it is paused. Check your dashboard for the current version.

Do I have to pay to stay on Postgres 14 on RDS?

AWS says RDS enrolls databases in Extended Support automatically after the end of standard support date, for a fee. That date is 28 February 2027 for version 14. Check AWS's pricing page for the current rate.

Sources

  1. PostgreSQL versioning policyPostgreSQL.org, accessed 15 Nov 2026
  2. Deprecation notice: Support for Postgres 14 ending on 1st July 2026Supabase changelog, 12 May 2026
  3. UpgradingSupabase docs, accessed 15 Nov 2026
  4. Release calendars for Amazon RDS for PostgreSQLAWS docs, accessed 15 Nov 2026
  5. Available PostgreSQL database versionsAWS docs, accessed 15 Nov 2026
  6. Amazon RDS for PostgreSQL pricingAWS, accessed 15 Nov 2026
  7. Postgres version policyNeon docs, accessed 15 Nov 2026
Technical consultation

Building something similar?

Talk to our engineering team about your architecture, roadmap, and delivery timeline.

Request a Technical Review →
ZoVintra Engineering Team

We design, engineer, and deploy high-performance web platforms, mobile applications, and intelligent cloud systems.

Related Reading

← Back to all posts