Add extension-update-test and pg-upgrade-stepwise CI jobs

[jnasbyupgrade]

Adds bin/test_existing (install→guard→update→assert→run-suite, modeled on Postgres-Extensions/cat_tools's own script of the same name) and bin/structural_diff, then wires two CI jobs on top of #18's local test/install/load.sql machinery: extension-update-test (0.1.0 → stable via ALTER EXTENSION UPDATE, structurally compared against a fresh install, then the full suite run against the real updated database) and pg-upgrade-stepwise (a binary pg_upgrade climb from the floor PostgreSQL major through every later supported major, re-proving the dependency guard at each step).

• bin/test_existing subcommands: plant-guard, update, prepare-old, run-suite, update-scenario, diff-fresh. prepare-old omits cat_tools's BRIDGE_TO parameter, and update-check/update-check-version aren't included — neither applies to this repo (see the script's own header for why).
• bin/structural_diff/bin/structural_diff.sql: generic per-extension structural comparison, copied from cat_tools without modification (already written generically, no cat_tools-specific object names). Wired into update-scenario as assert_matches_fresh.
• extension-update-test runs on a single PostgreSQL major (the newest supported) — 0.1.0 has no identified PostgreSQL-version floor, so crossing the full matrix would add job count with no added coverage.
• pg-upgrade-stepwise climbs the full matrix (12→18) on one cluster via a real binary pg_upgrade per step; the changes job now also derives climb_pg (the ascending major list) from the same NEWEST/CURRENT_FLOOR constants the test job's matrix already uses.
• all-checks-passed's needs: list and the top-of-file "Test strategy" comment are updated for both new jobs.

bin/test_existing's version assertion derives the current version from make -s print-EXTENSION_object_reference_VERSION, not print-PGXNVERSION (which cat_tools's own script uses) — this repo's PGXNVERSION is frozen at 0.1.0 (the last real numbered PGXN release) and no longer tracks the current build's default_version once the stable pseudo-version is in play, so the two diverge here in a way they don't for cat_tools.

Known issue: pg-upgrade-stepwise currently fails

The job's first binary pg_upgrade step fails restoring _sentry_mv (pg_class heap OID value not set when in binary upgrade mode) — a materialized view marked pg_extension_config_dump() cannot survive binary pg_upgrade. Confirmed as a general PostgreSQL limitation (reproduced independently against a bare, non-extension materialized view in a scratch cluster), not specific to this extension's own code. Fixing _sentry_mv needs a maintainer decision, since it's load-bearing for this extension's restore-repair contract — pg-upgrade-stepwise/all-checks-passed will stay red until that's resolved separately. lint, the test matrix, and extension-update-test are all green.

Also confirmed: diff-fresh exits non-zero on a genuine structural divergence (verified by deliberately corrupting a comment on a real table post-update), and its EXIT trap still drops the scratch reference database even when the failure isn't the trap-registering subshell's last command.

Co-Authored-By: Claude noreply@anthropic.com

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: aac09984-8287-4128-be86-d86a8170f1d6

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}