Skip to content

9.47.1 - #757

Merged
jeremydmiller merged 1 commit into
masterfrom
release/9.47.1
Oct 28, 2026
Merged

9.47.1#757
jeremydmiller merged 1 commit into
masterfrom
release/9.47.1

Conversation

@jeremydmiller

Copy link
Copy Markdown
Member

Patch release. One PostgreSQL fix, already on master, plus its release notes.

What is in it

  • #751 (closes #750), contributed by @marc-RocketRez — the index introspection query identified each row's table by regclassout's rendering of it and matched that against four spellings, none of which quoted the schema. Any schema that has to be quoted read back no indexes at all, so every declared index was Missing, the patch was a bare create index, and the second run answered 42P07 and aborted everything behind it.
  • #756 — tests for the two cases that fix closed without naming: a mixed-case schema, and the primary key constraint's name.

Why a patch

No working deployment changes behaviour. For a schema that needs no quoting, relname and regclassout's rendering name the same table and the comparison lands where it always did. In a schema that does need quoting, Weasel was unusable past the first run, so there is no old behaviour to preserve. Nothing public was added, removed or changed.

Release notes

Appended as a ## 9.47.1 section to docs/release-9-47.md, following 9.46.1's shape. The regclassout table in it is measured on PostgreSQL 15.3 rather than reasoned:

schema renders matched
public, in search_path docs yes, the bare candidate
reporting, not in search_path reporting.docs yes, the qualified candidate
order "order".docs no
MySchema "MySchema".docs no

The page builds locally with npm run docs-build.

🤖 Generated with Claude Code

One PostgreSQL fix, #750 / #751 contributed by @marc-RocketRez: the index
introspection query identified rows by regclassout's rendering of the
table, and none of the four spellings it compared against quoted the
schema. Any schema that has to be quoted -- a reserved word such as
order or user, or one carrying uppercase -- read back no indexes at all,
so every declared index was Missing, the patch was a bare create index,
and the second run answered 42P07 and aborted the rest of the migration.

The primary key constraint's name rides the same rows and was not read
back either; with a custom PK name that compared against the derived
default and emitted a rename off a constraint that was never there.

Nothing public added, removed or changed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@jeremydmiller
jeremydmiller merged commit ac66e26 into master Oct 28, 2026
21 checks passed
@jeremydmiller
jeremydmiller deleted the release/9.47.1 branch October 28, 2026 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

PostgreSQL index query reads back no indexes in a reserved-word schema ("order", "user")

1 participant