pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: David G. Johnston <david.g.johnston@gmail.com>
Cc: Vik Fearing <vik@2ndquadrant.fr>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: denisa.cirstescu@asentinel.com, "pgsql-docs@postgresql.org" <pgsql-docs@postgresql.org>
Subject: Re: Undocumented behavior od DROP SCHEMA ... CASCADE
Date: Fri, 12 Aug 2016 17:32:05 -0400
Message-ID: <20160812213205.GA717717@alvherre.pgsql> (raw)
In-Reply-To: <20493.1471035687@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>

Tom Lane wrote:
> Alvaro Herrera <alvherre@2ndquadrant.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.

True, but the DETAIL is capped at 100 objects (per
reportDependentObjects); also, object locks need to be acquired, which
can be very troublesome if you discover that some frequently-used object
is in the set to be dropped, by some unfortunate accident.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs



view thread (15+ messages)  latest in thread

Message-ID: <20160812213205.GA717717@alvherre.pgsql>
Permalink:  ../20160812213205.GA717717@alvherre.pgsql/
Also on:    postgresql.org/message-id/20160812213205.GA717717@alvherre.pgsql

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: alvherre@2ndquadrant.com, tgl@sss.pgh.pa.us, david.g.johnston@gmail.com, vik@2ndquadrant.fr, peter.eisentraut@2ndquadrant.com
  Subject: Re: Undocumented behavior od DROP SCHEMA ... CASCADE
  In-Reply-To: <20160812213205.GA717717@alvherre.pgsql>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox