Sample C — Red-flag fleet — PG12/13 already paying, self-managed PG11 past EOL, reg* columns, logical slots, prepared transactions, unknown extension and a missing rate.

Pgpilot report

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

Download Markdown · Download CSV · Plan another fleet

4 of 5 databases will pay for Extended Support: 3 are already paying for Extended Support (since 1 Mar 2025); 1 more starts on 1 Mar 2027 (RDS). If nothing moves: $4,123/month from 1 Dec 2026, $144,752 by 28 Feb 2030. Start with ancient-orders, old-billing and azure-old (already paying) and basement-server (past end of life).

Fleet total if nothing upgrades: $144,752 to 28 Feb 2030. Saving if all upgrade before their first charge: $0.

1 database has no fetched official rate for their region — costs show "enter rate" until you add a rate override. Fleet totals exclude them.

Monthly figures use 730 hours/month; totals to a deadline use exact hours between dates. Partial hours/minimums follow each provider's bill.

Fleet

DatabaseProvider/regionVersionCommunity EOLStandard endFirst chargeDays leftMonthly if slipTargetBlockersStatus
ancient-ordersRDS eu-west-212.17 (latest 12.22)Thu 21 Nov 2024Fri 28 Feb 2025Sat 1 Mar 2025-630$1,034185overdue
old-billingRDS eu-west-213.8 (latest 13.23)Thu 13 Nov 2025Sat 28 Feb 2026Sun 1 Mar 2026-265$2,756180overdue
basement-serverSelf-managed on-prem11.22Thu 9 Nov 2023Thu 9 Nov 2023——No paid option — unpatched since Thu 9 Nov 2023190overdue
no-rate-dbRDS ap-northeast-114.12 (latest 14.25)Thu 12 Nov 2026Sun 28 Feb 2027Mon 1 Mar 2027100enter rate181plan
azure-oldAzure Flexible uksouth13.14 (latest 13.23)Thu 13 Nov 2025Fri 31 Jul 2026Tue 1 Sep 2026-81$255181overdue

Monthly fleet cost

MonthFleet cost
November 2026$3,990
December 2026$4,123
January 2027$4,123
February 2027$3,724
March 2027$5,168 (excl. unknown rates)
April 2027$5,001 (excl. unknown rates)
May 2027$5,168 (excl. unknown rates)
June 2027$5,001 (excl. unknown rates)
July 2027$5,168 (excl. unknown rates)
August 2027$5,168 (excl. unknown rates)
September 2027$5,001 (excl. unknown rates)
October 2027$5,168 (excl. unknown rates)
November 2027$5,001 (excl. unknown rates)
December 2027$5,168 (excl. unknown rates)
January 2028$5,168 (excl. unknown rates)
February 2028$4,767 (excl. unknown rates)
March 2028$5,855 (excl. unknown rates)
April 2028$5,666 (excl. unknown rates)
May 2028$5,855 (excl. unknown rates)
June 2028$5,666 (excl. unknown rates)
July 2028$5,855 (excl. unknown rates)
August 2028$5,855 (excl. unknown rates)
September 2028$5,666 (excl. unknown rates)
October 2028$5,855 (excl. unknown rates)
November 2028$5,507 (excl. unknown rates)
December 2028$5,595 (excl. unknown rates)
January 2029$5,595 (excl. unknown rates)
February 2029$4,873 (excl. unknown rates)
March 2029$0 (excl. unknown rates)
April 2029$0 (excl. unknown rates)
May 2029$0 (excl. unknown rates)
June 2029$0 (excl. unknown rates)
July 2029$0 (excl. unknown rates)
August 2029$0 (excl. unknown rates)
September 2029$0 (excl. unknown rates)
October 2029$0 (excl. unknown rates)
November 2029$0 (excl. unknown rates)
December 2029$0 (excl. unknown rates)
January 2030$0 (excl. unknown rates)
February 2030$0 (excl. unknown rates)

Blockers

ancient-orders (PG12 → 18)

Enrolled in Extended Support: charges run from the first charge date until you upgrade or delete the database.

Charges begin the day after the RDS end of standard support date for enrolled databases. Disabling enrolment when already past that date triggers an automatic upgrade.

old-billing (PG13 → 18)

Extended Support enrolment disabled: if this database is past its standard support end (28 Feb 2026), AWS automatically upgrades it to the next supported major version. Do not wait for a surprise upgrade — schedule your own.

Charges begin the day after the RDS end of standard support date for enrolled databases. Disabling enrolment when already past that date triggers an automatic upgrade.

basement-server (PG11 → 19)

Self-managed: no patches after 2023-11-09 (community final release).

no-rate-db (PG14 → 18)

Enrolment unknown: check EngineLifecycleSupport in the console/CLI. This plan prices the enrolled case; disabled past the standard support end means an automatic upgrade instead of a bill.

Charges begin the day after the RDS end of standard support date for enrolled databases. Disabling enrolment when already past that date triggers an automatic upgrade.

azure-old (PG13 → 18)

Automatic enrolment; charges stop only by upgrading to a supported version. One-month grace period applies to versions 11, 12 and 13 only; billing starts 1 Sep 2026.

Release-note changes by jump

11 → 19

12 → 18

13 → 18

14 → 18

Next steps

  1. Sat 21 Nov 2026 [basement-server] Today: basement-server is past community end of life (no patches after 9 Nov 2023). Treat the upgrade as a security fix, not a cost choice. (pg-versioning-table)
  2. Sat 21 Nov 2026 [old-billing] Today: confirm RDS Extended Support enrolment for old-billing (disabled = AWS auto-upgrades it after 28 Feb 2026; enrolled = billing from 1 Mar 2026). (aws-enrolment)
  3. Sat 21 Nov 2026 [no-rate-db] Today: confirm RDS Extended Support enrolment for no-rate-db (disabled = AWS auto-upgrades it after 28 Feb 2027; enrolled = billing from 1 Mar 2027). (aws-enrolment)
  4. Sat 28 Nov 2026 [ancient-orders] Before upgrading ancient-orders: fix blocker — reg* columns block pg_upgrade. (pgupgrade-reg)
  5. Sat 28 Nov 2026 [ancient-orders] Before upgrading ancient-orders: fix blocker — Open prepared transactions. (rds-upgrade-prechecks)
  6. Sat 28 Nov 2026 [ancient-orders] Before upgrading ancient-orders: fix blocker — Logical replication slots / subscriptions. (rds-upgrade-prechecks)
  7. Sat 28 Nov 2026 [ancient-orders] Week of 28 Nov 2026: rehearse the 12 → 18 upgrade on a snapshot-restored copy of ancient-orders (staging rehearsal first, production last). (rds-upgrade-prechecks)
  8. Sat 28 Nov 2026 [azure-old] Before upgrading azure-old: fix blocker — adminpack removed in PostgreSQL 17. (release-17)
  9. Sat 28 Nov 2026 [azure-old] Week of 28 Nov 2026: rehearse the 13 → 18 upgrade on a snapshot-restored copy of azure-old (staging rehearsal first, production last). (azure-extended)
  10. Sat 28 Nov 2026 [basement-server] Week of 28 Nov 2026: rehearse the 11 → 19 upgrade on a snapshot-restored copy of basement-server (staging rehearsal first, production last). (pgupgrade)
  11. Sat 28 Nov 2026 [old-billing] Week of 28 Nov 2026: rehearse the 13 → 18 upgrade on a snapshot-restored copy of old-billing (staging rehearsal first, production last). (rds-upgrade-prechecks)
  12. Sat 28 Nov 2026 [no-rate-db] Before upgrading no-rate-db: fix blocker — plpython2u removed in PostgreSQL 15. (release-15)
  13. Sat 5 Dec 2026 [ancient-orders] By 5 Dec 2026: update ancient-orders to the latest minor (12.22) — you are on 12.17; minor currency is expected for upgrade pre-checks and Extended Support. (pg-versioning)
  14. Sat 5 Dec 2026 [azure-old] By 5 Dec 2026: update azure-old to the latest minor (13.23) — you are on 13.14; minor currency is expected for upgrade pre-checks and Extended Support. (pg-versioning)
  15. Sat 5 Dec 2026 [old-billing] By 5 Dec 2026: update old-billing to the latest minor (13.23) — you are on 13.8; minor currency is expected for upgrade pre-checks and Extended Support. (pg-versioning)
  16. Sat 5 Dec 2026 [no-rate-db] By 5 Dec 2026: update no-rate-db to the latest minor (14.25) — you are on 14.12; minor currency is expected for upgrade pre-checks and Extended Support. (pg-versioning)
  17. Sat 19 Dec 2026 [ancient-orders] By 19 Dec 2026: upgrade ancient-orders (prod) to PostgreSQL 18 — already paying Extended Support since Sat 1 Mar 2025; each month costs $1,034. (aws-calendar)
  18. Sat 19 Dec 2026 [ancient-orders] After upgrading ancient-orders: run ANALYZE, update extensions to their target versions, and recreate any logical replication slots you dropped. (rds-upgrade-prechecks)
  19. Sat 19 Dec 2026 [azure-old] By 19 Dec 2026: upgrade azure-old (prod) to PostgreSQL 18 — already paying Extended Support since Tue 1 Sep 2026; each month costs $255. (azure-extended)
  20. Sat 19 Dec 2026 [azure-old] After upgrading azure-old: run ANALYZE, update extensions to their target versions, and recreate any logical replication slots you dropped. (pgupgrade)
  21. Sat 19 Dec 2026 [basement-server] By 19 Dec 2026: upgrade basement-server (prod) to PostgreSQL 19 — past community end of life since 9 Nov 2023. (pgupgrade)
  22. Sat 19 Dec 2026 [basement-server] After upgrading basement-server: run ANALYZE, update extensions to their target versions, and recreate any logical replication slots you dropped. (pgupgrade)
  23. Sat 19 Dec 2026 [old-billing] By 19 Dec 2026: upgrade old-billing (prod) to PostgreSQL 18 — already paying Extended Support since Sun 1 Mar 2026; each month costs $2,756. (aws-calendar)
  24. Sat 19 Dec 2026 [old-billing] After upgrading old-billing: run ANALYZE, update extensions to their target versions, and recreate any logical replication slots you dropped. (rds-upgrade-prechecks)
  25. Mon 25 Jan 2027 [no-rate-db] Week of 25 Jan 2027: rehearse the 14 → 18 upgrade on a snapshot-restored copy of no-rate-db (staging rehearsal first, production last). (rds-upgrade-prechecks)
  26. Mon 15 Feb 2027 [no-rate-db] By 15 Feb 2027: upgrade no-rate-db (prod) to PostgreSQL 18 — two weeks before the first charge on 1 Mar 2027. (aws-calendar)
  27. Mon 15 Feb 2027 [no-rate-db] After upgrading no-rate-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 5 Postgres databases as of 21 Nov 2026. 4 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 **$144,752** in total to 28 Feb 2030, peaking at **$5,855 in March 2028**.
- If I upgrade everything before its first charge date, we save **$0** of that.
- Our most expensive database to delay is **old-billing** at **$2,756 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

- **ancient-orders**: 5 blockers — reg* columns block pg_upgrade; Open prepared transactions; Logical replication slots / subscriptions; tsearch2 is not supported on PostgreSQL 11 or later; chkpass is not supported on PostgreSQL 11 or later; 24 other release-note changes for 12 → 18 — see 'Release-note changes by jump' in the full report.
- **no-rate-db**: 1 blocker — plpython2u removed in PostgreSQL 15; PG15: Remove server-side language plpython2u and generic Python language plpythonu (release-15); 23 other release-note changes for 14 → 18 — see 'Release-note changes by jump' in the full report.
- **azure-old**: 1 blocker — adminpack removed in PostgreSQL 17; PG17: Remove adminpack contrib extension (release-17); 23 other release-note changes for 13 → 18 — see 'Release-note changes by jump' in the full report.

## The plan

- **21 Nov 2026** — Today: basement-server is past community end of life (no patches after 9 Nov 2023). Treat the upgrade as a security fix, not a cost choice.
- **21 Nov 2026** — Today: confirm RDS Extended Support enrolment for old-billing (disabled = AWS auto-upgrades it after 28 Feb 2026; enrolled = billing from 1 Mar 2026).
- **21 Nov 2026** — Today: confirm RDS Extended Support enrolment for no-rate-db (disabled = AWS auto-upgrades it after 28 Feb 2027; enrolled = billing from 1 Mar 2027).
- **28 Nov 2026** — Before upgrading ancient-orders: fix blocker — reg* columns block pg_upgrade.
- **28 Nov 2026** — Before upgrading ancient-orders: fix blocker — Open prepared transactions.
- **28 Nov 2026** — Before upgrading ancient-orders: fix blocker — Logical replication slots / subscriptions.
- **28 Nov 2026** — Week of 28 Nov 2026: rehearse the 12 → 18 upgrade on a snapshot-restored copy of ancient-orders (staging rehearsal first, production last).
- **28 Nov 2026** — Before upgrading azure-old: fix blocker — adminpack removed in PostgreSQL 17.
- **28 Nov 2026** — Week of 28 Nov 2026: rehearse the 13 → 18 upgrade on a snapshot-restored copy of azure-old (staging rehearsal first, production last).
- **28 Nov 2026** — Week of 28 Nov 2026: rehearse the 11 → 19 upgrade on a snapshot-restored copy of basement-server (staging rehearsal first, production last).
- **28 Nov 2026** — Week of 28 Nov 2026: rehearse the 13 → 18 upgrade on a snapshot-restored copy of old-billing (staging rehearsal first, production last).
- **28 Nov 2026** — Before upgrading no-rate-db: fix blocker — plpython2u removed in PostgreSQL 15.
- **5 Dec 2026** — By 5 Dec 2026: update ancient-orders to the latest minor (12.22) — you are on 12.17; minor currency is expected for upgrade pre-checks and Extended Support.
- **5 Dec 2026** — By 5 Dec 2026: update azure-old to the latest minor (13.23) — you are on 13.14; minor currency is expected for upgrade pre-checks and Extended Support.
- **5 Dec 2026** — By 5 Dec 2026: update old-billing to the latest minor (13.23) — you are on 13.8; minor currency is expected for upgrade pre-checks and Extended Support.
- **5 Dec 2026** — By 5 Dec 2026: update no-rate-db to the latest minor (14.25) — you are on 14.12; minor currency is expected for upgrade pre-checks and Extended Support.
- **19 Dec 2026** — By 19 Dec 2026: upgrade ancient-orders (prod) to PostgreSQL 18 — already paying Extended Support since Sat 1 Mar 2025; each month costs $1,034.
- **19 Dec 2026** — After upgrading ancient-orders: run ANALYZE, update extensions to their target versions, and recreate any logical replication slots you dropped.
- **19 Dec 2026** — By 19 Dec 2026: upgrade azure-old (prod) to PostgreSQL 18 — already paying Extended Support since Tue 1 Sep 2026; each month costs $255.
- **19 Dec 2026** — After upgrading azure-old: run ANALYZE, update extensions to their target versions, and recreate any logical replication slots you dropped.
- **19 Dec 2026** — By 19 Dec 2026: upgrade basement-server (prod) to PostgreSQL 19 — past community end of life since 9 Nov 2023.
- **19 Dec 2026** — After upgrading basement-server: run ANALYZE, update extensions to their target versions, and recreate any logical replication slots you dropped.
- **19 Dec 2026** — By 19 Dec 2026: upgrade old-billing (prod) to PostgreSQL 18 — already paying Extended Support since Sun 1 Mar 2026; each month costs $2,756.
- **19 Dec 2026** — After upgrading old-billing: run ANALYZE, update extensions to their target versions, and recreate any logical replication slots you dropped.
- **25 Jan 2027** — Week of 25 Jan 2027: rehearse the 14 → 18 upgrade on a snapshot-restored copy of no-rate-db (staging rehearsal first, production last).
- **15 Feb 2027** — By 15 Feb 2027: upgrade no-rate-db (prod) to PostgreSQL 18 — two weeks before the first charge on 1 Mar 2027.
- **15 Feb 2027** — After upgrading no-rate-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.

Why not just use…

Sources