Release cat_tools 0.2.2: fix PG11+ and PG12+ compatibility

[jnasbyupgrade]

Why This Release Exists

cat_tools 0.2.1 only installs correctly on PostgreSQL 9.2 – 10. Newer versions of
PostgreSQL changed system catalog internals in ways that break the 0.2.1 install script:

• PG 11 added pg_attribute.attmissingval (pseudo-type anyarray). Views cannot
  have anyarray columns; the 0.2.1 SELECT a.* from pg_attribute picks it up and
  fails at install time.
• PG 12 made system catalog oid columns visible as regular columns. Views using
  SELECT c.* alongside an explicit c.oid alias produce duplicate column names.

This means anyone on cat_tools 0.2.1 who upgrades PostgreSQL to version 11 or later
ends up with a broken extension. And there is no direct upgrade path from 0.2.1 to
0.3.0 — PostgreSQL automatically chains 0.2.1 → 0.2.2 → 0.3.0 when you run
ALTER EXTENSION cat_tools UPDATE, but only once 0.2.2 exists.

0.2.2 is that stepping stone. It installs and upgrades correctly on PostgreSQL 9.2
through 18+ (all currently supported versions).

Root Causes Fixed

PG 11+ (_cat_tools.pg_attribute_v): pg_attribute.attmissingval is anyarray,
which cannot be a view column. Fix: use omit_column() to exclude it from the SELECT *
expansion, then re-add it explicitly cast to text[] (or as NULL::text[] on PG ≤ 10).

PG 12+ (_cat_tools.pg_class_v, cat_tools.pg_extension_v): oid became a visible
column in system catalogs, causing SELECT c.oid AS reloid, c.* to produce duplicate
oid names. Fix: use omit_column() to exclude oid from the SELECT * expansion.

Upgrade Safety

Internal _cat_tools.* views are never directly accessed by users, so changes to them
are not a concern for user-owned views.

cat_tools.column is public, and it transitively exposes all columns of
_cat_tools.pg_attribute_v (via _cat_tools.column). Adding attmissingval anywhere
other than the end of the view chain would shift existing column positions, causing
CREATE OR REPLACE VIEW to fail with "cannot change name of view column" — even without
any user-dependent views.

The upgrade script handles this by using omit_column('_cat_tools.pg_attribute_v', array['attmissingval']) when rebuilding _cat_tools.column, so attmissingval is
appended after all pre-existing columns (column_type, base_type, pk_columns,
is_pk_member, column_default). This allows CREATE OR REPLACE VIEW on both
_cat_tools.column and cat_tools.column to succeed without requiring users to drop
views that depend on cat_tools.column.

Changes

• sql/cat_tools.sql.in: Three views rebuilt with omit_column() for dynamic column
  lists; attmissingval exposed as text[] in _cat_tools.pg_attribute_v (and
  transitively in _cat_tools.column / cat_tools.column)
• sql/cat_tools--0.2.1--0.2.2.sql.in: New upgrade script — safe CREATE OR REPLACE VIEW throughout; attmissingval placed at end of view chain via omit_column() on
  _cat_tools.pg_attribute_v
• cat_tools.control: default_version = '0.2.2'
• META.json / META.in.json: Version bumped to 0.2.2

Closes #2

🤖 Generated with Claude Code