You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Build cat_tools from its 0.3.0 git tag; adapt to its API/enum changes
pgxn install --unstable cat_tools resolves to the newest release actually
published to the PGXN package index, which is still 0.2.1 (2017) and fails
standalone on modern PostgreSQL with "column oid specified more than once"
at CREATE EXTENSION. A fixed release, 0.3.0, is tagged in cat_tools' own
git repo but hasn't been uploaded to PGXN yet, so the Makefile's cat_tools
target now clones Postgres-Extensions/cat_tools at the 0.3.0 tag and
builds/installs it directly.
Since this is the first time object_reference's suite has actually run
against a real, working cat_tools, two small fallout fixes are needed:
- cat_tools.function__arg_types_text() is deprecated in 0.3.0 in favor of
cat_tools.routine__parse_arg_types_text() (identical signature/body,
just renamed, deprecated one emits a WARNING on every call). Switched
object_reference's one call site to the non-deprecated name.
- cat_tools 0.3.0's object_type enum grew two new members, "partitioned
table" and "partitioned index". pg_get_object_address() doesn't
recognize either (only the base table/index types they derive from),
so object_reference classifies them as unsupported, matching
object_reference.unsupported()'s existing handling of "event trigger"
for the same reason. test/sql/all.sql's sanity-check of the unsupported
set is updated to match.
sql/object_reference--stable.sql and test/expected/zzz_build.out are
regenerated (make results) to match.
Extracted from PR #5, which had scope-crept into also carrying this fix
alongside the actual CI/pgxn-tools migration; splitting it out here so it
can be reviewed and merged independently.
0 commit comments