# Pgpilot — Postgres Extended Support plan

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

## Verdict

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

| Database | Provider/region | Version | Community EOL | Standard end | First charge | Days left | Monthly if slip | Target | Blockers | Status |
|---|---|---|---|---|---|---|---|---|---|---|
| ancient-orders | RDS eu-west-2 | 12.17 (latest 12.22) | Thu 21 Nov 2024 | Fri 28 Feb 2025 | Sat 1 Mar 2025 | -630 | $1,034 | 18 | 5 | overdue |
| old-billing | RDS eu-west-2 | 13.8 (latest 13.23) | Thu 13 Nov 2025 | Sat 28 Feb 2026 | Sun 1 Mar 2026 | -265 | $2,756 | 18 | 0 | overdue |
| basement-server | Self-managed on-prem | 11.22 | Thu 9 Nov 2023 | Thu 9 Nov 2023 | — | — | No paid option — unpatched since Thu 9 Nov 2023 | 19 | 0 | overdue |
| no-rate-db | RDS ap-northeast-1 | 14.12 (latest 14.25) | Thu 12 Nov 2026 | Sun 28 Feb 2027 | Mon 1 Mar 2027 | 100 | enter rate | 18 | 1 | plan |
| azure-old | Azure Flexible uksouth | 13.14 (latest 13.23) | Thu 13 Nov 2025 | Fri 31 Jul 2026 | Tue 1 Sep 2026 | -81 | $255 | 18 | 1 | overdue |

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

## Monthly fleet cost

| Month | Fleet cost |
|---|---|
| November 2026 | $3,990 |
| December 2026 | $4,123 |
| January 2027 | $4,123 |
| February 2027 | $3,724 |
| March 2027 | $5,168 |
| April 2027 | $5,001 |
| May 2027 | $5,168 |
| June 2027 | $5,001 |
| July 2027 | $5,168 |
| August 2027 | $5,168 |
| September 2027 | $5,001 |
| October 2027 | $5,168 |
| November 2027 | $5,001 |
| December 2027 | $5,168 |
| January 2028 | $5,168 |
| February 2028 | $4,767 |
| March 2028 | $5,855 |
| April 2028 | $5,666 |
| May 2028 | $5,855 |
| June 2028 | $5,666 |
| July 2028 | $5,855 |
| August 2028 | $5,855 |
| September 2028 | $5,666 |
| October 2028 | $5,855 |
| November 2028 | $5,507 |
| December 2028 | $5,595 |
| January 2029 | $5,595 |
| February 2029 | $4,873 |

## Blockers

### ancient-orders (PG12 → 18)
- [blocker] reg* columns block pg_upgrade — Remove uses of unsupported reg* types (regproc, regprocedure, regoper, regoperator, regconfig, regdictionary, regcollation, regnamespace) before upgrading; regclass, regdatabase, regrole and regtype can be upgraded. (pgupgrade-reg)
- [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)
- [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)
- [blocker] tsearch2 is not supported on PostgreSQL 11 or later — The tsearch2 extension is no longer supported for PostgreSQL versions 11 or later — drop it before upgrading. (rds-upgrade-prechecks)
- [blocker] chkpass is not supported on PostgreSQL 11 or later — The chkpass extension is no longer supported for PostgreSQL versions 11 or later — drop it before upgrading. (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)
- 24 other release-note changes for 12 → 18 — see 'Release-note changes by jump'

### old-billing (PG13 → 18)
- [warning] Heavy large-object use — Rehearse the upgrade on a snapshot-restored copy and time large-object handling; large objects lengthen pg_upgrade and any dump/restore fallback. (pgupgrade)
- [warning] Verify "mystery_ext" is available on PostgreSQL 18 — Extension "mystery_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'

### basement-server (PG11 → 19)
- [warning] Multi-major jump 11 → 19 — Read the release notes of all intervening major versions before upgrading (postgresql.org advice). (pg-upgrade-advice)
- 30 other release-note changes for 11 → 19 — see 'Release-note changes by jump'

### no-rate-db (PG14 → 18)
- [blocker] plpython2u removed in PostgreSQL 15 — Remove server-side language plpython2u and generic Python language plpythonu — Python 2 is no longer supported. (release-15)
- [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] 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'

### azure-old (PG13 → 18)
- [blocker] adminpack removed in PostgreSQL 17 — Remove adminpack contrib extension — removed in version 17. (release-17)
- [warning] Multi-major jump 13 → 18 — Read the release notes of all intervening major versions before upgrading (postgresql.org advice). (pg-upgrade-advice)
- [matched release note] PG17: Remove adminpack contrib extension (release-17)
- 23 other release-note changes for 13 → 18 — see 'Release-note changes by jump'

## Release-note changes by jump

### 11 → 19
- 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)
- PG19: Remove RADIUS support (release-19)
- PG19: Force standard_conforming_strings to always be on in the database server (release-19)
- PG19: Disallow carriage returns and line feeds in database, role, and tablespace names (release-19)
- PG19: Change the default index opclasses for inet and cidr data types from btree_gist to GiST (release-19)
- PG19: Change JIT to be disabled by default (release-19)
- PG19: Change default of max_locks_per_transaction from 64 to 128 (release-19)

### 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)

### 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)

## Next steps

- **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)
- **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)
- **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)
- **28 Nov 2026** [ancient-orders] Before upgrading ancient-orders: fix blocker — reg* columns block pg_upgrade. (pgupgrade-reg)
- **28 Nov 2026** [ancient-orders] Before upgrading ancient-orders: fix blocker — Open prepared transactions. (rds-upgrade-prechecks)
- **28 Nov 2026** [ancient-orders] Before upgrading ancient-orders: fix blocker — Logical replication slots / subscriptions. (rds-upgrade-prechecks)
- **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)
- **28 Nov 2026** [azure-old] Before upgrading azure-old: fix blocker — adminpack removed in PostgreSQL 17. (release-17)
- **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)
- **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)
- **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)
- **28 Nov 2026** [no-rate-db] Before upgrading no-rate-db: fix blocker — plpython2u removed in PostgreSQL 15. (release-15)
- **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)
- **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)
- **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)
- **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)
- **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)
- **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 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)
- **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)
- **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)
- **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)
- **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)
- **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 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)
- **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)
- **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.

## 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.
