cat_tools 0.2.3: fix pg_class.relkind mapping and the pg_upgrade update path

[jnasbyupgrade]

Release cat_tools 0.2.3.

Correct the backwards pg_class.relkind mapping in relation__kind() and relation__relkind(). Per pg_class.h, 'c' is a composite type, 'f' a foreign table, and 'm' a materialized view; releases through 0.2.2 had these three reversed.

Fix binary pg_upgrade failing for databases that reached 0.2.2 via the 0.2.0->0.2.2 or 0.2.1->0.2.2 update scripts. Those scripts filtered omitted columns with != ANY instead of != ALL; on a multi-element list != ANY strips nothing, so catalog columns removed in newer PostgreSQL (relhasoids, relhaspkey) remained in _cat_tools.pg_class_v and made pg_upgrade to PG12+ fail. Rather than re-issue the already-published 0.2.0->0.2.2 and 0.2.1->0.2.2 scripts, the 0.2.2->0.2.3 update repairs such a database at runtime: it detects the broken build (a relhasoids column still present on _cat_tools.pg_class_v) and only then drops and recreates the public view chain (cat_tools.pg_class_v, cat_tools.column, cat_tools.pg_class()) with the corrected column list. A fresh 0.2.2 install already has correct views, so the rebuild is skipped entirely and its views -- and any objects depending on them -- are left untouched. Because the repair is DROP+CREATE without CASCADE, a database that IS repaired must have any user objects depending on those public views dropped first and recreated afterward, or the update aborts.

Consequently, to binary-pg_upgrade a cluster whose cat_tools reached 0.2.2 via those update paths to PostgreSQL 12+, first ALTER EXTENSION cat_tools UPDATE to 0.2.3 (or newer); this is documented in README.asc and HISTORY.asc.

Track the generated sql/cat_tools--0.2.3.sql.in install script -- the nontrivial 0.2.2->0.2.3 update warrants committing it for update-test coverage and provenance -- and update CLAUDE.md's SQL-file-tracking rule accordingly. Also adds a RELEASE.md and a test/build/upgrade.sql regression guard proving a fresh 0.2.2 install's dependent objects survive the update to 0.2.3.

Verified on PostgreSQL 12 and 17 via the new test/build/upgrade.sql (a fresh 0.2.2 install with dependent views updates to 0.2.3 with those views left in place), and by master's extension-update-test (PG10), which installs 0.2.0, updates to current (0.2.0->0.2.2->0.2.3, exercising the conditional repair on a genuinely broken build), plus the explicit 0.2.1->0.2.2 leg.

[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: bb7de046-b788-4872-9aaa-424cd06d478b

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}