Upgrade readiness

The Upgrade Readiness tab assesses whether the connected instance is ready for a major version upgrade.

What it checks

• Deprecated / removed GUCs — parameters that have been removed or renamed in the next major version, with version-aware messaging
• Extension compatibility — installed extensions with known upgrade issues or compatibility requirements
• pg_upgrade blockers — catalog conditions that prevent pg_upgrade from succeeding
• Object patterns — legacy OID usage, incompatible extension versions, deprecated features

Caveats

pocketPG can only verify what is visible from SQL and catalog state. It cannot:

• test the actual upgrade
• estimate downtime
• check application-level compatibility
• assess extension behavior after upgrade

A staging environment with a representative workload is still required before upgrading production.

Integration

Upgrade readiness findings appear in the PDF health report alongside other operational assessments.