From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Tiffany Thang <tiffanythang(at)gmail(dot)com> |
Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Dropping dependent tables |
Date: | 2021-06-03 14:18:43 |
Message-ID: | 273406.1622729923@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tiffany Thang <tiffanythang(at)gmail(dot)com> writes:
> I would like to write a SQL statement to drop all the tables owned by me
> but a problem I’m struggling with is with referential integrity. The
> statement I have now to generate the drop statements is
> select 'drop table '||tablename||' cascade;' from pg_tables where
> tableowner='<myuseraccount>';
> The generated SQLs above might attempt to drop the parent tables first
> before the child and to be able to drop all the tables, I had to run the
> SQL script in multiple iterations. Not very clean.
Uh ... it's not clear to me why that wouldn't work. CASCADE should
be able to take care of foreign keys:
postgres=# create table t1 (f1 int primary key);
CREATE TABLE
postgres=# create table t2 (f2 int references t1);
CREATE TABLE
postgres=# drop table t1;
ERROR: cannot drop table t1 because other objects depend on it
DETAIL: constraint t2_f2_fkey on table t2 depends on table t1
HINT: Use DROP ... CASCADE to drop the dependent objects too.
postgres=# drop table t1 cascade;
NOTICE: drop cascades to constraint t2_f2_fkey on table t2
DROP TABLE
Could you enlarge on what problem you saw, specifically?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Hans Buschmann | 2021-06-03 17:56:10 | LZ4 missing in pg14-beta1 Windows build, OLD VS/compiler used |
Previous Message | Tiffany Thang | 2021-06-03 13:41:53 | Dropping dependent tables |