abhsss/pg-upgrade repository overview

Docker images that automate PostgreSQL major-version upgrades using pg_upgrade, built for teams running containerized PostgreSQL in production.

Each image contains both the old and new PostgreSQL binaries. The upgrade runs in three isolated container steps connected by Docker volumes (or Kubernetes PersistentVolumeClaims), so no data ever leaves your infrastructure.

⁠Supported upgrade paths

⁠Quick start

# Step 1 — seed the old cluster with test data
docker run --rm \
  -v pg-old-data:/var/lib/postgresql/13/main \
  abhsss/pg-upgrade:13-to-16 init-old

# Step 2 — run pg_upgrade (prints before/after snapshots and timing)
docker run --rm \
  -v pg-old-data:/var/lib/postgresql/13/main \
  -v pg-new-data:/var/lib/postgresql/16/main \
  abhsss/pg-upgrade:13-to-16 upgrade

# Step 3 — verify integrity of the upgraded cluster
docker run --rm \
  -v pg-new-data:/var/lib/postgresql/16/main \
  abhsss/pg-upgrade:13-to-16 verify

⁠What the upgrade step prints

• Directory snapshot of the old cluster (sizes, config files)
• Structural renames applied (pg_xlog → pg_wal, pg_clog → pg_xact, etc.)
• Directory snapshot of the new cluster after upgrade
• Size delta and wall-clock duration
• Locations of the generated analyze_new_cluster.sh and delete_old_cluster.sh scripts

⁠What the verify step prints

• Per-database size report (queried live from pg_database)
• Pass/fail count across all integrity checks (row counts, indexes, views, sequences, foreign keys, materialized views)

⁠No credentials required

pg_upgrade works directly on data files as the postgres OS user. No database password is involved at any stage of the upgrade.

⁠Kubernetes

The image runs unmodified on Kubernetes. Replace Docker volumes with PersistentVolumeClaims and docker run with Jobs. Full manifests and step-by-step instructions are in the GitHub repository⁠.

⁠Source

github.com/abhsss96/postgres-upgrade-kit⁠