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
| Database | Provider/region | Version | Community EOL | Standard end | First charge | Days left | Monthly if slip | Target | Blockers | Status |
|---|---|---|---|---|---|---|---|---|---|---|
| orders-db | RDS eu-west-2 | 14.12 (latest 14.25) | Thu 12 Nov 2026 | Sun 28 Feb 2027 | Mon 1 Mar 2027 | 100 | $2,756 | 18 | 1 | plan |
| billing-db | RDS eu-west-2 | 14.10 (latest 14.25) | Thu 12 Nov 2026 | Sun 28 Feb 2027 | Mon 1 Mar 2027 | 100 | $1,034 | 18 | 1 | plan |
| auth-db | Cloud SQL europe-west2 | 14.9 (latest 14.25) | Thu 12 Nov 2026 | — | Mon 1 Feb 2027 | 72 | $613 | 18 | 0 | urgent |
| analytics-db | Azure Flexible uksouth | 14.11 (latest 14.25) | Thu 12 Nov 2026 | Sun 31 Jan 2027 | Mon 1 Feb 2027 | 72 | $1,022 | 18 | 0 | urgent |
| legacy-erp-db | RDS eu-west-2 | 13.15 (latest 13.23) | Thu 13 Nov 2025 | Sat 28 Feb 2026 | Sun 1 Mar 2026 | -265 | $345 | 18 | 1 | overdue |
| reports-db | Cloud SQL europe-west2 | 13.11 (latest 13.23) | Thu 13 Nov 2025 | — | Sun 1 Feb 2026 | -293 | $102 | 18 | 0 | overdue |
| catalog-db | RDS eu-west-2 | 15.6 (latest 15.20) | Thu 11 Nov 2027 | Tue 29 Feb 2028 | Wed 1 Mar 2028 | 466 | $1,034 | 18 | 0 | OK |
| search-db | Azure Flexible uksouth | 16.2 (latest 16.16) | Thu 9 Nov 2028 | Thu 9 Nov 2028 | — | — | — | 18 | 0 | OK |
| staging-orders | RDS eu-west-2 | 14.12 (latest 14.25) | Thu 12 Nov 2026 | Sun 28 Feb 2027 | Mon 1 Mar 2027 | 100 | $172 | 18 | 0 | plan |
Monthly fleet cost
| Month | Fleet 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)
- [blocker] Logical replication slots / subscriptions — An RDS upgrade can't occur if the database has any logical replication slots (on source version 17 and later, slots on non-read-replicas can be retained). Plan to drop and recreate slots and subscriptions around the upgrade. (rds-upgrade-prechecks)
- [warning] Update "postgis" for PostgreSQL 18 — Check the available "postgis" version on the target and update it after the upgrade (for example ALTER EXTENSION … UPDATE where your provider requires it). (rds-upgrade-prechecks)
- [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 14 → 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 14 → 18 — see 'Release-note changes by jump'
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)
- [blocker] Open prepared transactions — Commit or roll back all open prepared transactions before attempting an upgrade (check pg_catalog.pg_prepared_xacts). (rds-upgrade-prechecks)
- [warning] Update "pgcrypto" for PostgreSQL 18 — Check the available "pgcrypto" 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 14 → 18 — Read the release notes of all intervening major versions before upgrading (postgresql.org advice). (pg-upgrade-advice)
- 24 other release-note changes for 14 → 18 — see 'Release-note changes by jump'
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)
- [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). (pgupgrade)
- [warning] Update "citext" for PostgreSQL 18 — Check the available "citext" version on the target and update it after the upgrade (for example ALTER EXTENSION … UPDATE where your provider requires it). (pgupgrade)
- [warning] Multi-major jump 14 → 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 14 → 18 — see 'Release-note changes by jump'
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)
- [warning] Update "timescaledb" for PostgreSQL 18 — Check the available "timescaledb" version on the target and update it after the upgrade (for example ALTER EXTENSION … UPDATE where your provider requires it). (pgupgrade)
- [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). (pgupgrade)
- [warning] Multi-major jump 14 → 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 14 → 18 — see 'Release-note changes by jump'
Automatic enrolment; charges stop only by upgrading to a supported version. No grace period is listed for this version.
legacy-erp-db (PG13 → 18)
- [blocker] Custom C extension — Shared object files matching the new server binary must be installed in the new cluster; confirm a build exists for the target major before scheduling. (pgupgrade)
- [warning] Update "pg_trgm" for PostgreSQL 18 — Check the available "pg_trgm" version on the target and update it after the upgrade (for example ALTER EXTENSION … UPDATE where your provider requires it). (rds-upgrade-prechecks)
- [warning] Verify "acme_custom_ext" is available on PostgreSQL 18 — Extension "acme_custom_ext" is not in this planner's known list. Confirm it exists for the target major on your provider before scheduling; this planner only calls an extension unsupported when a fetched source says so. (rds-upgrade-prechecks)
- [warning] Multi-major jump 13 → 18 — Read the release notes of all intervening major versions before upgrading (postgresql.org advice). (pg-upgrade-advice)
- 24 other release-note changes for 13 → 18 — see 'Release-note changes by jump'
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)
- [warning] Update "postgis" for PostgreSQL 18 — Check the available "postgis" version on the target and update it after the upgrade (for example ALTER EXTENSION … UPDATE where your provider requires it). (pgupgrade)
- [warning] Multi-major jump 13 → 18 — Read the release notes of all intervening major versions before upgrading (postgresql.org advice). (pg-upgrade-advice)
- 24 other release-note changes for 13 → 18 — see 'Release-note changes by jump'
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)
- [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 15 → 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)
- 17 other release-note changes for 15 → 18 — see 'Release-note changes by jump'
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)
- [warning] Update "pg_trgm" for PostgreSQL 18 — Check the available "pg_trgm" version on the target and update it after the upgrade (for example ALTER EXTENSION … UPDATE where your provider requires it). (pgupgrade)
- [warning] Update "unaccent" for PostgreSQL 18 — Check the available "unaccent" version on the target and update it after the upgrade (for example ALTER EXTENSION … UPDATE where your provider requires it). (pgupgrade)
- [warning] Multi-major jump 16 → 18 — Read the release notes of all intervening major versions before upgrading (postgresql.org advice). (pg-upgrade-advice)
- 12 other release-note changes for 16 → 18 — see 'Release-note changes by jump'
Extended Support dates for this major were not published on the fetched Azure page (table covers 11–14).
staging-orders (PG14 → 18)
- [warning] Update "postgis" for PostgreSQL 18 — Check the available "postgis" 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 14 → 18 — Read the release notes of all intervening major versions before upgrading (postgresql.org advice). (pg-upgrade-advice)
- 24 other release-note changes for 14 → 18 — see 'Release-note changes by jump'
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
- 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)
14 → 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)
15 → 18
- 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)
16 → 18
- 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
- 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)
- 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)
- Sat 28 Nov 2026 [legacy-erp-db] Before upgrading legacy-erp-db: fix blocker — Custom C extension. (pgupgrade)
- 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)
- 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)
- Sat 28 Nov 2026 [billing-db] Before upgrading billing-db: fix blocker — Open prepared transactions. (rds-upgrade-prechecks)
- Sat 28 Nov 2026 [orders-db] Before upgrading orders-db: fix blocker — Logical replication slots / subscriptions. (rds-upgrade-prechecks)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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…
- endoflife.date/postgresql — community end-of-life dates only; no per-provider Extended Support charges or fleet costs.
- Cloud pricing calculators — price one instance at a time; they do not order a mixed fleet by charge date or list upgrade blockers.
- why-upgrade.depesz.com — shows what changes between two Postgres majors (features and config changes); no cloud support deadlines or costs.
Sources
- PostgreSQL versioning policy — https://www.postgresql.org/support/versioning/ (fetched 21 Nov 2026)
“The PostgreSQL Global Development Group supports a major version for 5 years after its initial release. After this, a final minor version will be released and the software will then be unsupported (end-of-life).” - PostgreSQL versioning table (current minor / final release) — https://www.postgresql.org/support/versioning/ (fetched 21 Nov 2026)
“14 | 14.25 | No | September 30, 2021 | November 12, 2026” - PostgreSQL upgrading advice — https://www.postgresql.org/support/versioning/ (fetched 21 Nov 2026)
“You can upgrade from one major version to another without upgrading to intervening versions, but we recommend reading the release notes of all intervening major versions prior to doing so.” - PostgreSQL 19 release (press page banner) — https://www.postgresql.org/about/press/ (fetched 21 Nov 2026)
“November 19, 2026: PostgreSQL 19 Released!” - pg_upgrade documentation — https://www.postgresql.org/docs/current/pgupgrade.html (fetched 21 Nov 2026)
“Install extension shared object files — Many extensions and custom modules, whether from contrib or another source, use shared object files (or DLLs), e.g., pgcrypto.so. If the old cluster used these, shared object files matching the new server binary must be installed in the new cluster” - pg_upgrade restrictions (reg* types) — https://www.postgresql.org/docs/current/pgupgrade.html (fetched 21 Nov 2026)
“regcollation | regconfig | regdictionary | regnamespace | regoper | regoperator | regproc | regprocedure | (regclass, regdatabase, regrole, and regtype can be upgraded.)” - RDS for PostgreSQL release calendar — https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html (fetched 21 Nov 2026)
“PostgreSQL 14 | 30 September 2021 | 3 February 2022 | 12 November 2026 | 28 February 2027 | 1 March 2027 | 1 March 2029 | 28 February 2030” - Amazon RDS Extended Support charges — https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support-charges.html (fetched 21 Nov 2026)
“You will incur charges for all engines enrolled in RDS Extended Support beginning the day after the RDS end of standard support date. … RDS Extended Support charges apply to standby instances in Multi-AZ deployments.” - Amazon RDS Extended Support (enrolment) — https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support.html (fetched 21 Nov 2026)
“If you disable the enrollment status of a DB instance or DB cluster that is already past its standard support end date, the instance or cluster automatically upgrades to the next supported major version.” - Amazon RDS Extended Support (3-year limit) — https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support.html (fetched 21 Nov 2026)
“RDS Extended Support is available for up to 3 years past the RDS end of standard support date for a major engine version. After this time, if you haven't upgraded your major engine version to a supported version, then Amazon RDS will automatically upgrade your major engine version.” - RDS for PostgreSQL pricing (Extended Support) — https://aws.amazon.com/rds/postgresql/pricing/ (fetched 21 Nov 2026)
“For provisioned instances on RDS for PostgreSQL, RDS Extended Support is priced per vCPU per hour. RDS Extended Support pricing is also dependent on the AWS Region and calendar date.” - RDS Extended Support pricing example (AWS) — https://aws.amazon.com/rds/postgresql/pricing/ (fetched 21 Nov 2026)
“If you have an instance on RDS for PostgreSQL 12, this version reaches end of standard support on February 28, 2025. If you are deployed in US East (Ohio), you will be charged $0.100 per vCPU-hr between March 1, 2025 to February 28, 2027. Starting March 1, 2027, you will be charged $0.200 per vCPU-hr.” - RDS pricing (partial hours) — https://aws.amazon.com/rds/postgresql/pricing/ (fetched 21 Nov 2026)
“Partial hours are billed in one-second increments with a 10-minute minimum charge following a billable status change such as creating, starting, or modifying.” - 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 (fetched 21 Nov 2026)
“"description": "USD 0.10 per hour per vCPU running RDS Extended Support for PostgreSQL 13 in Year 1, Year 2", "unit": "vCPU-hour", "pricePerUnit": {"USD": "0.1000000000"}” - Aurora PostgreSQL release calendar — https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/aurorapostgresql-release-calendar.html (fetched 21 Nov 2026)
“PostgreSQL 14 | 30 September 2021 | November 2026 | … | 28 February 2027 | 1 March 2027 | 1 March 2029 | 28 February 2030” - RDS major version upgrade process / prechecks — https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Process.html (fetched 21 Nov 2026)
“During the major version upgrade process, Amazon RDS for PostgreSQL first runs a precheck procedure to identify any issues that might cause the upgrade to fail.” - Azure Database for PostgreSQL extended support — https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/extended-support (fetched 21 Nov 2026)
“14 | June 29, 2022 | November 12, 2026 | January 31, 2027 | February 1, 2027 | November 11, 2029” - Azure extended support grace period — https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/extended-support (fetched 21 Nov 2026)
“Grace period: A one-month grace period is provided for PostgreSQL versions 11, 12, and 13. Extended support billing starts on September 1, 2026.” - Azure extended support enrolment — https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/extended-support (fetched 21 Nov 2026)
“No. Extended support is automatically applied to eligible servers running unsupported PostgreSQL versions. To stop extended support charges, upgrade to a supported PostgreSQL version.” - Azure PostgreSQL version policy — https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/concepts-version-policy (fetched 21 Nov 2026)
“PostgreSQL 19 (preview, East Asia only) | Release notes | 19-Nov-2026 | 12-Nov-2031” - Azure Retail Prices API — Extended Support vCore — https://prices.azure.com/api/retail/prices (fetched 21 Nov 2026)
“"meterName":"Extended Support vCore","productName":"Azure Database for Postgres Extended Support","unitOfMeasure":"1 Hour"” - Cloud SQL database versions — https://docs.cloud.google.com/sql/docs/db-versions (fetched 21 Nov 2026)
“PostgreSQL 14 | 14.24 | November 11, 2021 | February 1, 2027 | February 1, 2030” - Extended support for Cloud SQL — https://cloud.google.com/sql/docs/postgres/extended-support (fetched 21 Nov 2026)
“An instance can be in extended support for three years. After a major version has reached three years in extended support, the major version is deprecated. When a major version is deprecated, Cloud SQL upgrades all deprecated major version instances to the default major version automatically.” - Cloud SQL pricing — extended support — https://cloud.google.com/sql/pricing (fetched 21 Nov 2026)
“For dedicated-core instances, extended support is priced per vCPU per hour and charged for every second that the instance is running.” - Cloud SQL pricing table (extended support) — https://cloud.google.com/sql/pricing (fetched 21 Nov 2026)
“vCPUs | $0.07 / 1 hour | $0.14 / 1 hour | HA vCPUs | $0.14 / 1 hour | $0.28 / 1 hour” - PostgreSQL 15 release notes — Migration to Version 15 — https://www.postgresql.org/docs/release/15.0/ (fetched 21 Nov 2026)
“Version 15 contains a number of changes that may affect compatibility with previous releases.” - PostgreSQL 16 release notes — Migration to Version 16 — https://www.postgresql.org/docs/release/16.0/ (fetched 21 Nov 2026)
“Version 16 contains a number of changes that may affect compatibility with previous releases.” - PostgreSQL 17 release notes — Migration to Version 17 — https://www.postgresql.org/docs/release/17.0/ (fetched 21 Nov 2026)
“Version 17 contains a number of changes that may affect compatibility with previous releases.” - PostgreSQL 18 release notes — Migration to Version 18 — https://www.postgresql.org/docs/release/18.0/ (fetched 21 Nov 2026)
“Version 18 contains a number of changes that may affect compatibility with previous releases.” - PostgreSQL 19 release notes — Migration to Version 19 — https://www.postgresql.org/docs/release/19.0/ (fetched 21 Nov 2026)
“Version 19 contains a number of changes that may affect compatibility with previous releases.”