Synthetic lab report

PostgreSQL 14 → 18: an upgrade decision record

An illustrative readiness report based on a reproducible self-managed lab. Generated data only; this is not a customer engagement or an RDS/Aurora rehearsal.

Synthetic example. The recorded observations below come from the published lab script and output run on 21 October 2026. No client data or client outcome is represented.

Scope and inventory

ItemLab evidenceDecision use
EnginePostgreSQL 14.24 → 18.6, self-managed Docker/PGDG packagesPath applies to this lab only
DataGenerated orders table, 500,000 rowsRepresentative of this test, not a client workload
ExtensionsUpgrade check logged “Checking for extension updates … ok”; a complete extension version matrix was not capturedReal review requires pg_extension inventory and target availability
Replicationpgoutput logical slot debezium_orders and publication cdc_pubCDC consumer restart and reconciliation need an owner
ChecksumsPG14 cluster off; PG18 default initialization onCluster creation settings must match for pg_upgrade

Compatibility and blockers

CheckObservedAction before go
Data checksumsInitial check failed with mismatched settingsInitialize target consistently, or choose and test another migration path
Prepared transactionCheck failed until open transaction was rolled backResolve with application owner; prevent recreation during cutover
regproc columnCheck failed until the lab column was converted to textReview application semantics and schema migration
Logical slot / CDCCheck passed with the slot present; slot was absent after upgradePlan CDC position, recreation and downstream reconciliation
Planner statisticsLab ran staged analyze after upgradeInclude statistics rebuild and workload comparison in runbook

Representative workload baseline

The lab records a 500,000-row orders table but does not record pre/post query latency or plans. Therefore it cannot establish performance readiness. A client report would include agreed query fingerprints, plans, p95/p99 latency, call volume, waits and error rate from comparable windows. The go decision stays pending until that evidence exists.

Risk register

  • High: CDC continuity. The logical slot did not survive the tested path. Owner: data pipeline team. Validation: no missing or duplicate downstream events after a documented restart point.
  • High: application compatibility. Driver/ORM and extension versions were not inventoried. Owner: application team. Validation: target-version staging tests.
  • Medium: post-upgrade plan change. No representative baseline was captured. Owner: performance reviewer. Validation: compare critical query fingerprints before and after on the same workload.
  • Medium: rollback feasibility. pg_upgrade --link has different recovery constraints from a copy-based path. Owner: operations. Validation: rehearse restore/switchover and set a cutover decision time.

Go / no-go checklist

  • ☐ Target engine, extension and driver compatibility verified.
  • ☐ pg_upgrade --check passes on the final rehearsal copy.
  • ☐ Prepared transactions and schema blockers are resolved.
  • ☐ CDC consumers, positions and reconciliation owner are documented.
  • ☐ Critical query baseline and post-upgrade thresholds are agreed.
  • ☐ Restore path, backup integrity and rollback decision time are rehearsed.

Illustrative decision: no-go until the unmeasured workload and CDC recovery criteria are documented and tested. Passing the mechanical upgrade check alone is insufficient.

See the full upgrade checklist and review scope.