Upgrade track

PostgreSQL Upgrade Readiness Review

Identify blockers and performance-regression risks before a major-version change. Build a representative baseline, test critical plans and agree on go/no-go and rollback criteria.

PostgreSQL 14 deadline:Community fixes end 12 November 2026. On Amazon RDS and Aurora, standard support ends 28 February 2027, with Extended Support year-1 pricing starting 1 March 2027. Some 14.x minor versions lose standard support sooner.See the dates →

Why the mechanics are not the hard part

On RDS and Aurora, a major-version upgrade or a blue/green switchover is a documented, mostly managed operation, and pg_upgrade --check catches many blockers on self-managed servers. What those tools do not tell you is how your own workload will behave on the new version: which plans change, which queries slow down until statistics are rebuilt, which extension or driver behaves differently, and how you would know within the first hour.

This review is about that part: evidence from your workload before the change, a short list of what to compare after it, and clear go/no-go and rollback criteria.

Inventory

Version + extensions

Identify extension and application dependencies that can affect the target-version path.

Performance

Baseline before change

Capture representative workload behavior so regressions are observable rather than anecdotal.

Validation

Know what to compare

Define critical queries, plans, latency and operational checks for the post-upgrade window.

Typical review areas

  • Current engine and extension inventory
  • Target-version choice and support horizon
  • Application/ORM compatibility checklist
  • Major plan-regression risks
  • Staging/replay strategy
  • Pre-upgrade workload baseline
  • Post-upgrade validation and rollback considerations
  • RDS/Aurora-specific path where relevant

What you send

  • Platform (RDS, Aurora or self-managed), current version and the target you are considering
  • Extension list with versions: SELECT extname, extversion FROM pg_extension;
  • Output of the read-only evidence collector as the pre-upgrade baseline
  • Client drivers, ORM and connection pooler versions
  • Any planned change window, replicas, logical replication or CDC consumers

What you receive

  • A written readiness report: blockers, risks ranked by likelihood and impact, and the evidence for each
  • A recommended upgrade path and target version for your platform, with its trade-offs
  • The critical queries and plans to compare before and after, plus the latency and error signals to watch
  • Go/no-go and rollback criteria for the change window
  • A review call with your team

Price

Fixed quote after fit review for one cluster, agreed current and target versions, representative workload and major blockers. Fee and delivery date depend on extension count, platform, baseline evidence and availability; both are agreed before work starts. See how quoting works.

Ask about upgrade readiness

Review a synthetic readiness report based on the reproducible self-managed upgrade lab.

To run the checks yourself first, use the PostgreSQL 14 upgrade checklist. For the most common post-upgrade slowdown, see why PostgreSQL can be slow after a major upgrade.

Important: I do not execute the production upgrade as part of this review unless separately scoped. Your team or managed-service provider owns the change window.

Upgrade readiness

Planning a major PostgreSQL upgrade?

Start with your version, platform and extension list. The first step is scoping the smallest useful readiness review.

Prefer to talk first? Book a 20-minute triage call.