Sample A — Northwind Ledger Ltd (Sam's fleet) — Fictional 9-database fleet: 4 on PG14, 2 on PG13, rest 15–16 across RDS eu-west-2, Cloud SQL europe-west2 and Azure uksouth.

Pgpilot report

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

Download Markdown · Download CSV · Plan another fleet

8 of 9 databases will pay for Extended Support: 2 are already paying for Extended Support (since 1 Feb 2026); 6 more start on 1 Feb 2027 (Cloud SQL, Azure Flexible), then 1 Mar 2027 (RDS), then 1 Mar 2028 (RDS). If nothing moves: $455/month from 1 Dec 2026, $320,345 by 28 Feb 2031. Start with legacy-erp-db and reports-db (already paying), then orders-db (largest cost at $2,756/month, 1 blocker).

Fleet total if nothing upgrades: $320,345 to 28 Feb 2031. Saving if all upgrade before their first charge: $302,633.

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
orders-dbRDS eu-west-214.12 (latest 14.25)Thu 12 Nov 2026Sun 28 Feb 2027Mon 1 Mar 2027100$2,756181plan
billing-dbRDS eu-west-214.10 (latest 14.25)Thu 12 Nov 2026Sun 28 Feb 2027Mon 1 Mar 2027100$1,034181plan
auth-dbCloud SQL europe-west214.9 (latest 14.25)Thu 12 Nov 2026—Mon 1 Feb 202772$613180urgent
analytics-dbAzure Flexible uksouth14.11 (latest 14.25)Thu 12 Nov 2026Sun 31 Jan 2027Mon 1 Feb 202772$1,022180urgent
legacy-erp-dbRDS eu-west-213.15 (latest 13.23)Thu 13 Nov 2025Sat 28 Feb 2026Sun 1 Mar 2026-265$345181overdue
reports-dbCloud SQL europe-west213.11 (latest 13.23)Thu 13 Nov 2025—Sun 1 Feb 2026-293$102180overdue
catalog-dbRDS eu-west-215.6 (latest 15.20)Thu 11 Nov 2027Tue 29 Feb 2028Wed 1 Mar 2028466$1,034180OK
search-dbAzure Flexible uksouth16.2 (latest 16.16)Thu 9 Nov 2028Thu 9 Nov 2028———180OK
staging-ordersRDS eu-west-214.12 (latest 14.25)Thu 12 Nov 2026Sun 28 Feb 2027Mon 1 Mar 2027100$172180plan

Monthly fleet cost

MonthFleet cost
November 2026$441
December 2026$455
January 2027$455
February 2027$1,917
March 2027$6,160
April 2027$5,962
May 2027$6,160
June 2027$5,962
July 2027$6,160
August 2027$6,160
September 2027$5,962
October 2027$6,160
November 2027$5,962
December 2027$6,160
January 2028$6,160
February 2028$5,860
March 2028$7,666
April 2028$7,419
May 2028$7,666
June 2028$7,419
July 2028$7,666
August 2028$7,666
September 2028$7,419
October 2028$7,666
November 2028$7,419
December 2028$7,666
January 2029$7,666
February 2029$7,278
March 2029$11,388
April 2029$11,020
May 2029$11,388
June 2029$11,020
July 2029$11,388
August 2029$11,388
September 2029$11,020
October 2029$11,388
November 2029$10,348
December 2029$10,346
January 2030$10,346
February 2030$7,956
March 2030$2,098
April 2030$2,030
May 2030$2,098
June 2030$2,030
July 2030$2,098
August 2030$2,098
September 2030$2,030
October 2030$2,098
November 2030$2,030
December 2030$2,098
January 2031$2,098
February 2031$1,827

Blockers

orders-db (PG14 → 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.

billing-db (PG14 → 18)

Extended Support enrolment disabled: if this database is past its standard support end (28 Feb 2027), 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.

auth-db (PG14 → 18)

Auto-enrolled and billed from the extended support start date. At deprecation, Cloud SQL automatically upgrades instances to the default major version.

analytics-db (PG14 → 18)

Automatic enrolment; charges stop only by upgrading to a supported version. No grace period is listed for this version.

legacy-erp-db (PG13 → 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.

reports-db (PG13 → 18)

Auto-enrolled and billed from the extended support start date. At deprecation, Cloud SQL automatically upgrades instances to the default major version.

catalog-db (PG15 → 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.

search-db (PG16 → 18)

Extended Support dates for this major were not published on the fetched Azure page (table covers 11–14).

staging-orders (PG14 → 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.

Release-note changes by jump

13 → 18

14 → 18

15 → 18

16 → 18

Next steps

  1. Sat 21 Nov 2026 [legacy-erp-db] Today: confirm RDS Extended Support enrolment for legacy-erp-db (disabled = AWS auto-upgrades it after 28 Feb 2026; enrolled = billing from 1 Mar 2026). (aws-enrolment)
  2. Sat 21 Nov 2026 [billing-db] Today: confirm RDS Extended Support enrolment for billing-db (disabled = AWS auto-upgrades it after 28 Feb 2027; enrolled = billing from 1 Mar 2027). (aws-enrolment)
  3. Sat 28 Nov 2026 [legacy-erp-db] Before upgrading legacy-erp-db: fix blocker — Custom C extension. (pgupgrade)
  4. Sat 28 Nov 2026 [legacy-erp-db] Week of 28 Nov 2026: rehearse the 13 → 18 upgrade on a snapshot-restored copy of legacy-erp-db (staging rehearsal first, production last). (rds-upgrade-prechecks)
  5. Sat 28 Nov 2026 [reports-db] Week of 28 Nov 2026: rehearse the 13 → 18 upgrade on a snapshot-restored copy of reports-db (staging rehearsal first, production last). (gcp-extended)
  6. Sat 28 Nov 2026 [billing-db] Before upgrading billing-db: fix blocker — Open prepared transactions. (rds-upgrade-prechecks)
  7. Sat 28 Nov 2026 [orders-db] Before upgrading orders-db: fix blocker — Logical replication slots / subscriptions. (rds-upgrade-prechecks)
  8. Sat 5 Dec 2026 [legacy-erp-db] By 5 Dec 2026: update legacy-erp-db to the latest minor (13.23) — you are on 13.15; minor currency is expected for upgrade pre-checks and Extended Support. (pg-versioning)
  9. Sat 5 Dec 2026 [reports-db] By 5 Dec 2026: update reports-db to the latest minor (13.23) — you are on 13.11; minor currency is expected for upgrade pre-checks and Extended Support. (pg-versioning)
  10. Sat 5 Dec 2026 [analytics-db] By 5 Dec 2026: update analytics-db to the latest minor (14.25) — you are on 14.11; minor currency is expected for upgrade pre-checks and Extended Support. (pg-versioning)
  11. Sat 5 Dec 2026 [auth-db] By 5 Dec 2026: update auth-db to the latest minor (14.25) — you are on 14.9; minor currency is expected for upgrade pre-checks and Extended Support. (pg-versioning)
  12. Sat 5 Dec 2026 [staging-orders] By 5 Dec 2026: update staging-orders to the latest minor (14.25) — you are on 14.12; minor currency is expected for upgrade pre-checks and Extended Support. (pg-versioning)
  13. Sat 5 Dec 2026 [billing-db] By 5 Dec 2026: update billing-db to the latest minor (14.25) — you are on 14.10; minor currency is expected for upgrade pre-checks and Extended Support. (pg-versioning)
  14. Sat 5 Dec 2026 [orders-db] By 5 Dec 2026: update orders-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)
  15. Sat 5 Dec 2026 [catalog-db] By 5 Dec 2026: update catalog-db to the latest minor (15.20) — you are on 15.6; minor currency is expected for upgrade pre-checks and Extended Support. (pg-versioning)
  16. Sat 5 Dec 2026 [search-db] By 5 Dec 2026: update search-db to the latest minor (16.16) — you are on 16.2; minor currency is expected for upgrade pre-checks and Extended Support. (pg-versioning)
  17. Sat 19 Dec 2026 [legacy-erp-db] By 19 Dec 2026: upgrade legacy-erp-db (prod) to PostgreSQL 18 — already paying Extended Support since Sun 1 Mar 2026; each month costs $345. (aws-calendar)
  18. Sat 19 Dec 2026 [legacy-erp-db] After upgrading legacy-erp-db: run ANALYZE, update extensions to their target versions, and recreate any logical replication slots you dropped. (rds-upgrade-prechecks)
  19. Sat 19 Dec 2026 [reports-db] By 19 Dec 2026: upgrade reports-db (prod) to PostgreSQL 18 — already paying Extended Support since Sun 1 Feb 2026; each month costs $102. (gcp-versions)
  20. Sat 19 Dec 2026 [reports-db] After upgrading reports-db: run ANALYZE, update extensions to their target versions, and recreate any logical replication slots you dropped. (pgupgrade)
  21. Mon 28 Dec 2026 [analytics-db] Week of 28 Dec 2026: rehearse the 14 → 18 upgrade on a snapshot-restored copy of analytics-db (staging rehearsal first, production last). (azure-extended)
  22. Mon 28 Dec 2026 [auth-db] Week of 28 Dec 2026: rehearse the 14 → 18 upgrade on a snapshot-restored copy of auth-db (staging rehearsal first, production last). (gcp-extended)
  23. Mon 18 Jan 2027 [analytics-db] By 18 Jan 2027: upgrade analytics-db (prod) to PostgreSQL 18 — two weeks before the first charge on 1 Feb 2027. (azure-extended)
  24. Mon 18 Jan 2027 [analytics-db] After upgrading analytics-db: run ANALYZE, update extensions to their target versions, and recreate any logical replication slots you dropped. (pgupgrade)
  25. Mon 18 Jan 2027 [auth-db] By 18 Jan 2027: upgrade auth-db (prod) to PostgreSQL 18 — two weeks before the first charge on 1 Feb 2027. (gcp-versions)
  26. Mon 18 Jan 2027 [auth-db] After upgrading auth-db: run ANALYZE, update extensions to their target versions, and recreate any logical replication slots you dropped. (pgupgrade)
  27. Mon 18 Jan 2027 [staging-orders] Week of 18 Jan 2027: rehearse the 14 → 18 upgrade on a snapshot-restored copy of staging-orders. (rds-upgrade-prechecks)
  28. Mon 25 Jan 2027 [billing-db] Week of 25 Jan 2027: rehearse the 14 → 18 upgrade on a snapshot-restored copy of billing-db (staging rehearsal first, production last). (rds-upgrade-prechecks)
  29. Mon 25 Jan 2027 [orders-db] Week of 25 Jan 2027: rehearse the 14 → 18 upgrade on a snapshot-restored copy of orders-db (staging rehearsal first, production last). (rds-upgrade-prechecks)
  30. Mon 8 Feb 2027 [staging-orders] By 8 Feb 2027: upgrade staging-orders (staging) to PostgreSQL 18 — before the first charge on 1 Mar 2027. (aws-calendar)
  31. Mon 8 Feb 2027 [staging-orders] After upgrading staging-orders: run ANALYZE, update extensions to their target versions, and recreate any logical replication slots you dropped. (rds-upgrade-prechecks)
  32. Mon 15 Feb 2027 [billing-db] By 15 Feb 2027: upgrade billing-db (prod) to PostgreSQL 18 — two weeks before the first charge on 1 Mar 2027. (aws-calendar)
  33. Mon 15 Feb 2027 [billing-db] After upgrading billing-db: run ANALYZE, update extensions to their target versions, and recreate any logical replication slots you dropped. (rds-upgrade-prechecks)
  34. Mon 15 Feb 2027 [orders-db] By 15 Feb 2027: upgrade orders-db (prod) to PostgreSQL 18 — two weeks before the first charge on 1 Mar 2027. (aws-calendar)
  35. Mon 15 Feb 2027 [orders-db] After upgrading orders-db: run ANALYZE, update extensions to their target versions, and recreate any logical replication slots you dropped. (rds-upgrade-prechecks)
  36. Wed 26 Jan 2028 [catalog-db] Week of 26 Jan 2028: rehearse the 15 → 18 upgrade on a snapshot-restored copy of catalog-db (staging rehearsal first, production last). (rds-upgrade-prechecks)
  37. Wed 16 Feb 2028 [catalog-db] By 16 Feb 2028: upgrade catalog-db (prod) to PostgreSQL 18 — two weeks before the first charge on 1 Mar 2028. (aws-calendar)
  38. Wed 16 Feb 2028 [catalog-db] After upgrading catalog-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 9 Postgres databases as of 21 Nov 2026. 8 of them will start paying for Extended Support, first on 1 Feb 2026. 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 **$320,345** in total to 28 Feb 2031, peaking at **$11,388 in March 2029**.
- If I upgrade everything before its first charge date, we save **$302,633** of that.
- Our most expensive database to delay is **orders-db** 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

- **orders-db**: 1 blocker — Logical replication slots / subscriptions; PG17: Rename I/O block read/write timing statistics columns of pg_stat_statements (release-17); 23 other release-note changes for 14 → 18 — see 'Release-note changes by jump' in the full report.
- **billing-db**: 1 blocker — Open prepared transactions; 24 other release-note changes for 14 → 18 — see 'Release-note changes by jump' in the full report.
- **auth-db**: PG17: Rename I/O block read/write timing statistics columns of pg_stat_statements (release-17); 23 other release-note changes for 14 → 18 — see 'Release-note changes by jump' in the full report.
- **analytics-db**: PG17: Rename I/O block read/write timing statistics columns of pg_stat_statements (release-17); 23 other release-note changes for 14 → 18 — see 'Release-note changes by jump' in the full report.
- **legacy-erp-db**: 1 blocker — Custom C extension; 24 other release-note changes for 13 → 18 — see 'Release-note changes by jump' in the full report.
- **catalog-db**: PG17: Rename I/O block read/write timing statistics columns of pg_stat_statements (release-17); 17 other release-note changes for 15 → 18 — see 'Release-note changes by jump' in the full report.

## The plan

- **21 Nov 2026** — Today: confirm RDS Extended Support enrolment for legacy-erp-db (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 billing-db (disabled = AWS auto-upgrades it after 28 Feb 2027; enrolled = billing from 1 Mar 2027).
- **28 Nov 2026** — Before upgrading legacy-erp-db: fix blocker — Custom C extension.
- **28 Nov 2026** — Week of 28 Nov 2026: rehearse the 13 → 18 upgrade on a snapshot-restored copy of legacy-erp-db (staging rehearsal first, production last).
- **28 Nov 2026** — Week of 28 Nov 2026: rehearse the 13 → 18 upgrade on a snapshot-restored copy of reports-db (staging rehearsal first, production last).
- **28 Nov 2026** — Before upgrading billing-db: fix blocker — Open prepared transactions.
- **28 Nov 2026** — Before upgrading orders-db: fix blocker — Logical replication slots / subscriptions.
- **5 Dec 2026** — By 5 Dec 2026: update legacy-erp-db to the latest minor (13.23) — you are on 13.15; minor currency is expected for upgrade pre-checks and Extended Support.
- **5 Dec 2026** — By 5 Dec 2026: update reports-db to the latest minor (13.23) — you are on 13.11; minor currency is expected for upgrade pre-checks and Extended Support.
- **5 Dec 2026** — By 5 Dec 2026: update analytics-db to the latest minor (14.25) — you are on 14.11; minor currency is expected for upgrade pre-checks and Extended Support.
- **5 Dec 2026** — By 5 Dec 2026: update auth-db to the latest minor (14.25) — you are on 14.9; minor currency is expected for upgrade pre-checks and Extended Support.
- **5 Dec 2026** — By 5 Dec 2026: update staging-orders to the latest minor (14.25) — you are on 14.12; minor currency is expected for upgrade pre-checks and Extended Support.
- **5 Dec 2026** — By 5 Dec 2026: update billing-db to the latest minor (14.25) — you are on 14.10; minor currency is expected for upgrade pre-checks and Extended Support.
- **5 Dec 2026** — By 5 Dec 2026: update orders-db to the latest minor (14.25) — you are on 14.12; minor currency is expected for upgrade pre-checks and Extended Support.
- **5 Dec 2026** — By 5 Dec 2026: update catalog-db to the latest minor (15.20) — you are on 15.6; minor currency is expected for upgrade pre-checks and Extended Support.
- **5 Dec 2026** — By 5 Dec 2026: update search-db to the latest minor (16.16) — you are on 16.2; minor currency is expected for upgrade pre-checks and Extended Support.
- **19 Dec 2026** — By 19 Dec 2026: upgrade legacy-erp-db (prod) to PostgreSQL 18 — already paying Extended Support since Sun 1 Mar 2026; each month costs $345.
- **19 Dec 2026** — After upgrading legacy-erp-db: run ANALYZE, update extensions to their target versions, and recreate any logical replication slots you dropped.
- **19 Dec 2026** — By 19 Dec 2026: upgrade reports-db (prod) to PostgreSQL 18 — already paying Extended Support since Sun 1 Feb 2026; each month costs $102.
- **19 Dec 2026** — After upgrading reports-db: run ANALYZE, update extensions to their target versions, and recreate any logical replication slots you dropped.
- **28 Dec 2026** — Week of 28 Dec 2026: rehearse the 14 → 18 upgrade on a snapshot-restored copy of analytics-db (staging rehearsal first, production last).
- **28 Dec 2026** — Week of 28 Dec 2026: rehearse the 14 → 18 upgrade on a snapshot-restored copy of auth-db (staging rehearsal first, production last).
- **18 Jan 2027** — By 18 Jan 2027: upgrade analytics-db (prod) to PostgreSQL 18 — two weeks before the first charge on 1 Feb 2027.
- **18 Jan 2027** — After upgrading analytics-db: run ANALYZE, update extensions to their target versions, and recreate any logical replication slots you dropped.
- **18 Jan 2027** — By 18 Jan 2027: upgrade auth-db (prod) to PostgreSQL 18 — two weeks before the first charge on 1 Feb 2027.
- **18 Jan 2027** — After upgrading auth-db: run ANALYZE, update extensions to their target versions, and recreate any logical replication slots you dropped.
- **18 Jan 2027** — Week of 18 Jan 2027: rehearse the 14 → 18 upgrade on a snapshot-restored copy of staging-orders.
- **25 Jan 2027** — Week of 25 Jan 2027: rehearse the 14 → 18 upgrade on a snapshot-restored copy of billing-db (staging rehearsal first, production last).
- **25 Jan 2027** — Week of 25 Jan 2027: rehearse the 14 → 18 upgrade on a snapshot-restored copy of orders-db (staging rehearsal first, production last).
- **8 Feb 2027** — By 8 Feb 2027: upgrade staging-orders (staging) to PostgreSQL 18 — before the first charge on 1 Mar 2027.

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