Skip to content
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

CREATE TABLE IF NOT EXISTS PARTITION OF raise error instead of just skip #2087

Closed
gwierzchowski opened this issue Apr 7, 2018 · 2 comments · Fixed by #4507
Closed

CREATE TABLE IF NOT EXISTS PARTITION OF raise error instead of just skip #2087

gwierzchowski opened this issue Apr 7, 2018 · 2 comments · Fixed by #4507
Assignees
Milestone

Comments

@gwierzchowski
Copy link

CREATE TABLE "test2" (
   "cdc" INTEGER,
   "product" INTEGER)
PARTITION BY LIST ("cdc");
-- ok
SELECT create_distributed_table('test2', 'product');
-- ok
CREATE TABLE "test2_1" PARTITION OF "test2" for values in (1);
-- ok
CREATE TABLE IF NOT EXISTS "test2_1" PARTITION OF "test2" FOR VALUES IN (1); 
NOTICE:  relation "test2_1" already exists, skipping
ERROR:  table "test2_1" is already distributed

It should just give notice without error (how it is on plain PG).
Under Python this raises psycopg2.ProgrammingError.

Citus 7.3, PG 10.3 started from docker-compose on Linux Mint 18.3

@marcocitus marcocitus added the bug label Apr 9, 2018
@ozgune
Copy link
Contributor

ozgune commented Jul 7, 2018

@gwierzchowski -- Thank you for reporting this bug.

@metdos -- Do we know how long the fix would take?

@l-we
Copy link

l-we commented May 28, 2020

Is there any progress

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants