rent extension check

rent extension check reads extension declarations from rent/schema.rsl, inspects the live PostgreSQL server, selects compatible versions, and reports missing privileges, unavailable extensions, preload requirements, provider restrictions, and dependency problems before migration time.

Check a self-hosted server

rent extension check

Extension preflight

READY              vector (0.8.1)
READY              pgmq (1.5.1)
BLOCKED            pg_cron
  - shared_preload_libraries is missing pg_cron

The command exits unsuccessfully when any declared extension is blocked, so it can guard environment setup and deployment.

Apply a hosted-provider policy

rent extension check --provider supabase

Extension preflight

READY              vector (0.8.1)
READY              pgmq (1.5.1)

Supported policy names are self-hosted, supabase, neon, aws, google-cloud, and azure. Rent still discovers the real server capabilities; the provider policy adds known operational restrictions and guidance.

Produce JSON for automation

rent extension check --format json

[
  {
    "extension": "vector",
    "selected_version": "0.8.1",
    "issues": [],
    "ready": true,
    "restart_required": false
  },
  {
    "extension": "pg_cron",
    "selected_version": "1.6.4",
    "issues": [
      {
        "MissingPreloadLibrary": "pg_cron"
      }
    ],
    "ready": false,
    "restart_required": true
  }
]

Each issues entry is one typed preflight issue: PostgresTooOld, UnsupportedPostgresMajor, NoCompatibleVersion, RequestedVersionUnavailable, MissingPreloadLibrary, SuperuserRequired, ProviderDisallows, ProviderEnablementRequired, NonRelocatableSchema, ExternalBinaryRequired, or ProviderRestartUnavailable. When no version can be selected, selected_version is null and the issues include NoCompatibleVersion or RequestedVersionUnavailable. restart_required is true when resolving the issues needs a server restart. The exact selected version comes from the connected server, not from this example.