# Pgpilot — Postgres Extended Support plan

As of 21 Nov 2026 · Planning aid, not a vendor quote.

## Verdict

1 of 1 database will pay for Extended Support: 1 is already paying for Extended Support (since 1 Mar 2025). If nothing moves: $298/month from 1 Dec 2026, $8,160 by 29 Feb 2028. Start with aws-worked-example-db (already paying).

## Fleet

| Database | Provider/region | Version | Community EOL | Standard end | First charge | Days left | Monthly if slip | Target | Blockers | Status |
|---|---|---|---|---|---|---|---|---|---|---|
| aws-worked-example-db | RDS us-east-2 | 12.22 | Thu 21 Nov 2024 | Fri 28 Feb 2025 | Sat 1 Mar 2025 | -630 | $292 | 18 | 0 | overdue |

Fleet total if nothing upgrades: **$8,160** to 29 Feb 2028. Saving if all upgrade before their first charge: **$0**.

## Monthly fleet cost

| Month | Fleet cost |
|---|---|
| November 2026 | $288 |
| December 2026 | $298 |
| January 2027 | $298 |
| February 2027 | $269 |
| March 2027 | $595 |
| April 2027 | $576 |
| May 2027 | $595 |
| June 2027 | $576 |
| July 2027 | $595 |
| August 2027 | $595 |
| September 2027 | $576 |
| October 2027 | $595 |
| November 2027 | $576 |
| December 2027 | $595 |
| January 2028 | $595 |
| February 2028 | $538 |

## Blockers

### aws-worked-example-db (PG12 → 18)
- [warning] Update "pg_stat_statements" for PostgreSQL 18 — Check the available "pg_stat_statements" version on the target and update it after the upgrade (for example ALTER EXTENSION … UPDATE where your provider requires it). (rds-upgrade-prechecks)
- [warning] Multi-major jump 12 → 18 — Read the release notes of all intervening major versions before upgrading (postgresql.org advice). (pg-upgrade-advice)
- [matched release note] PG17: Rename I/O block read/write timing statistics columns of pg_stat_statements (release-17)
- 23 other release-note changes for 12 → 18 — see 'Release-note changes by jump'

## Release-note changes by jump

### 12 → 18
- PG15: Remove PUBLIC creation permission on the public schema (release-15)
- PG15: Change the owner of the public schema to be the new pg_database_owner role (release-15)
- PG15: Remove long-deprecated exclusive backup mode (release-15)
- PG15: Remove server-side language plpython2u and generic Python language plpythonu (release-15)
- PG15: Prevent numeric literals from having non-numeric trailing characters (release-15)
- PG15: Generate an error if array_to_tsvector() is passed an empty-string array element (release-15)
- PG16: Change assignment rules for PL/pgSQL bound cursor variables (release-16)
- PG16: Disallow NULLS NOT DISTINCT indexes for primary keys (release-16)
- PG16: Remove the ability to create views manually with ON SELECT rules (release-16)
- PG16: Remove the server variable vacuum_defer_cleanup_age (release-16)
- PG16: Remove server variable promote_trigger_file (release-16)
- PG16: Restrict the privileges of CREATEROLE and its ability to modify other roles (release-16)
- PG17: Change functions to use a safe search_path during maintenance operations (release-17)
- PG17: Remove server variable old_snapshot_threshold (release-17)
- PG17: Remove adminpack contrib extension (release-17)
- PG17: Remove buffers_backend and buffers_backend_fsync from pg_stat_bgwriter (release-17)
- PG17: Rename I/O block read/write timing statistics columns of pg_stat_statements (release-17)
- PG17: Rename pg_collation.colliculocale to colllocale and pg_database.daticulocale to datlocale (release-17)
- PG18: Change initdb default to enable data checksums (release-18)
- PG18: Deprecate MD5 password authentication (release-18)
- PG18: Change VACUUM and ANALYZE to process the inheritance children of a parent (release-18)
- PG18: Disallow unlogged partitioned tables (release-18)
- PG18: Report RESTRICT foreign key violations with SQLSTATE 23001 (restrict_violation) instead of 23503 (foreign_key_violation) (release-18)
- PG18: Change full text search to use the default collation provider of the cluster to read configuration files and dictionaries, rather than always using libc (release-18)

## Next steps

- **28 Nov 2026** [aws-worked-example-db] Week of 28 Nov 2026: rehearse the 12 → 18 upgrade on a snapshot-restored copy of aws-worked-example-db (staging rehearsal first, production last). (rds-upgrade-prechecks)
- **19 Dec 2026** [aws-worked-example-db] By 19 Dec 2026: upgrade aws-worked-example-db (prod) to PostgreSQL 18 — already paying Extended Support since Sat 1 Mar 2025; each month costs $292. (aws-calendar)
- **19 Dec 2026** [aws-worked-example-db] After upgrading aws-worked-example-db: run ANALYZE, update extensions to their target versions, and recreate any logical replication slots you dropped. (rds-upgrade-prechecks)

## CTO brief

# Postgres upgrade plan — I need a decision before the first Extended Support bill

I have audited our 1 Postgres database as of 21 Nov 2026. 1 of them will start paying for Extended Support, first on 1 Mar 2025. PostgreSQL 14 reached community end of life on 12 Nov 2026 and our clouds now charge to keep running it.

## What waiting costs

- If nothing moves, Extended Support costs us **$8,160** in total to 29 Feb 2028, peaking at **$595 in March 2027**.
- If I upgrade everything before its first charge date, we save **$0** of that.
- Our most expensive database to delay is **aws-worked-example-db** at **$292 per month**, so I want to move it first.

## What I am asking for

I need approval to run the dated upgrade plan below: rehearse each upgrade on a snapshot copy, do staging before production, and finish each production upgrade at least two weeks before its first charge date where that date is still ahead of us — and within four weeks for databases already paying. I also need a short maintenance window per production database. If we slip, the meter is already priced — each month of delay is a bill, not a backlog item.

## What could block us

- **aws-worked-example-db**: PG17: Rename I/O block read/write timing statistics columns of pg_stat_statements (release-17); 23 other release-note changes for 12 → 18 — see 'Release-note changes by jump' in the full report.

## The plan

- **28 Nov 2026** — Week of 28 Nov 2026: rehearse the 12 → 18 upgrade on a snapshot-restored copy of aws-worked-example-db (staging rehearsal first, production last).
- **19 Dec 2026** — By 19 Dec 2026: upgrade aws-worked-example-db (prod) to PostgreSQL 18 — already paying Extended Support since Sat 1 Mar 2025; each month costs $292.
- **19 Dec 2026** — After upgrading aws-worked-example-db: run ANALYZE, update extensions to their target versions, and recreate any logical replication slots you dropped.

I will report back after the first rehearsal with timings and any extension blockers I find. The full per-database breakdown, blockers and sources are in the Pgpilot report this brief came from.

— Sam, Platform Engineering

Pgpilot · Daily Ships · Planning aid, not a vendor quote. Dates and Extended Support rates follow postgresql.org, AWS, Microsoft and Google Cloud documentation (checked 21 Nov 2026); your provider's bill and console decide.

## Sources (fetched 21 Nov 2026)

- PostgreSQL versioning policy: https://www.postgresql.org/support/versioning/
- PostgreSQL versioning table (current minor / final release): https://www.postgresql.org/support/versioning/
- PostgreSQL upgrading advice: https://www.postgresql.org/support/versioning/
- PostgreSQL 19 release (press page banner): https://www.postgresql.org/about/press/
- pg_upgrade documentation: https://www.postgresql.org/docs/current/pgupgrade.html
- pg_upgrade restrictions (reg* types): https://www.postgresql.org/docs/current/pgupgrade.html
- RDS for PostgreSQL release calendar: https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html
- Amazon RDS Extended Support charges: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support-charges.html
- Amazon RDS Extended Support (enrolment): https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support.html
- Amazon RDS Extended Support (3-year limit): https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support.html
- RDS for PostgreSQL pricing (Extended Support): https://aws.amazon.com/rds/postgresql/pricing/
- RDS Extended Support pricing example (AWS): https://aws.amazon.com/rds/postgresql/pricing/
- RDS pricing (partial hours): https://aws.amazon.com/rds/postgresql/pricing/
- AWS Price List API — Amazon RDS offers (filtered to Extended Support): https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonRDS/current/region_index.json
- Aurora PostgreSQL release calendar: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/aurorapostgresql-release-calendar.html
- RDS major version upgrade process / prechecks: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Process.html
- Azure Database for PostgreSQL extended support: https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/extended-support
- Azure extended support grace period: https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/extended-support
- Azure extended support enrolment: https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/extended-support
- Azure PostgreSQL version policy: https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/concepts-version-policy
- Azure Retail Prices API — Extended Support vCore: https://prices.azure.com/api/retail/prices
- Cloud SQL database versions: https://docs.cloud.google.com/sql/docs/db-versions
- Extended support for Cloud SQL: https://cloud.google.com/sql/docs/postgres/extended-support
- Cloud SQL pricing — extended support: https://cloud.google.com/sql/pricing
- Cloud SQL pricing table (extended support): https://cloud.google.com/sql/pricing
- PostgreSQL 15 release notes — Migration to Version 15: https://www.postgresql.org/docs/release/15.0/
- PostgreSQL 16 release notes — Migration to Version 16: https://www.postgresql.org/docs/release/16.0/
- PostgreSQL 17 release notes — Migration to Version 17: https://www.postgresql.org/docs/release/17.0/
- PostgreSQL 18 release notes — Migration to Version 18: https://www.postgresql.org/docs/release/18.0/
- PostgreSQL 19 release notes — Migration to Version 19: https://www.postgresql.org/docs/release/19.0/

Pgpilot · Daily Ships · Planning aid, not a vendor quote. Dates and Extended Support rates follow postgresql.org, AWS, Microsoft and Google Cloud documentation (checked 21 Nov 2026); your provider's bill and console decide.
