Skip to content

Name the extension of the CREATE INDEX operator - #4

Merged
redox merged 1 commit into
altertable-v2.0-cyanopterafrom
su/postgres-create-index-extension-name
Nov 13, 2026
Merged

redox merged 1 commit into
altertable-v2.0-cyanopterafrom
su/postgres-create-index-extension-name

Conversation

@redox

@redox redox commented Nov 13, 2026

Copy link
Copy Markdown
Member

LogicalPostgresCreateIndex didn't override GetExtensionName(), whose default throws Serialization Error: LogicalExtensionOperator::GetExtensionName not implemented…. Optimizer hooks of other extensions call it on every extension operator (match_recognize does), so CREATE INDEX on an attached Postgres database failed when one was loaded. Since altertable-ai/ducklake-private#26, that includes ATTACH 'ducklake:postgres:…'.

It now returns "postgres_scanner". The root cause is fixed in match_recognize too (altertable-ai/duckdb-match_recognize, same branch name). This keeps other hooks from tripping on the same operator.

Tested against a local Postgres 16 with the unfixed match_recognize: ATTACH 'ducklake:postgres:…' now succeeds and creates DuckLake's two stats indexes.

🤖 Generated with Claude Code

LogicalExtensionOperator::GetExtensionName() throws by default. Optimizer
hooks of other extensions (match_recognize) call it on every extension
operator in a plan, so CREATE INDEX on an attached Postgres database
failed when one was loaded.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@redox
redox merged commit cacc25d into altertable-v2.0-cyanoptera Nov 13, 2026
4 checks passed
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.

1 participant