8000 DROP TABLE on partitioned table causes "Invalid Input Error" on all subsequent queries · Issue #69 · duckdb/ducklake · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

DROP TABLE on partitioned table causes "Invalid Input Error" on all subsequent queries #69

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
csmithxc opened this issue May 28, 2025 · 1 comment · Fixed by #75
Closed

Comments

@csmithxc
Copy link

Setup:

  • Postgres catalog (Supabase, Postgres 15.8.1)
  • S3 data path
  • DuckDB 1.3.0 via CLI

Reproduce:

CREATE TABLE IF NOT EXISTS test_update AS (SELECT 1 as id, 'hello' as greeting, 60 as amount) WITH NO DATA;
INSERT INTO test_update SELECT 1 as id, 'hello' as greeting, 60 as amount;
ALTER TABLE test_update SET PARTITIONED BY (greeting);

DROP TABLE test_update;

-- Can be literally any query
SHOW ALL TABLES;

Resulting error:

  • Invalid Input Error: Could not find matching table for partition entry
@Mytherin
Copy link
Contributor

Thanks for the report! I've pushed a fix in #75

Mytherin added a commit that referenced this issue May 28, 2025
Fix #69: when a table is dropped, also drop any partitioning info associated with that table
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants
0