| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Vik Fearing <vik(at)2ndquadrant(dot)fr>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, denisa(dot)cirstescu(at)asentinel(dot)com, "pgsql-docs(at)postgresql(dot)org" <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: Undocumented behavior od DROP SCHEMA ... CASCADE |
| Date: | 2016-08-12 21:01:27 |
| Message-ID: | 20493.1471035687@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> I think it'd be a good idea to add some more discoverability: what would
> be deleted if an object X were to be deleted?
There's plenty of discoverability already. The documentation suggests
(If you want to check what <command>DROP ... CASCADE</> will do,
run <command>DROP</> without <literal>CASCADE</> and read the
<literal>DETAIL</> output.)
Or you could do BEGIN; DROP ... CASCADE; ROLLBACK.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-08-12 21:32:05 | Re: Undocumented behavior od DROP SCHEMA ... CASCADE |
| Previous Message | Alvaro Herrera | 2016-08-12 20:55:08 | Re: Undocumented behavior od DROP SCHEMA ... CASCADE |