Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bYJaY-0003G5-5o for pgsql-docs@arkaria.postgresql.org; Fri, 12 Aug 2016 21:01:58 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bYJaX-00054t-Og for pgsql-docs@arkaria.postgresql.org; Fri, 12 Aug 2016 21:01:57 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bYJaB-0004gu-Lz for pgsql-docs@postgresql.org; Fri, 12 Aug 2016 21:01:35 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bYJa9-0002GQ-B8 for pgsql-docs@postgresql.org; Fri, 12 Aug 2016 21:01:34 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id u7CL1RY0020494; Fri, 12 Aug 2016 17:01:27 -0400 From: Tom Lane To: Alvaro Herrera cc: "David G. Johnston" , Vik Fearing , Peter Eisentraut , denisa.cirstescu@asentinel.com, "pgsql-docs@postgresql.org" Subject: Re: Undocumented behavior od DROP SCHEMA ... CASCADE In-reply-to: <20160812205508.GA714477@alvherre.pgsql> References: <20160812205508.GA714477@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Fri, 12 Aug 2016 16:55:08 -0400" Date: Fri, 12 Aug 2016 17:01:27 -0400 Message-ID: <20493.1471035687@sss.pgh.pa.us> X-Pg-Spam-Score: -2.4 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org Alvaro Herrera 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 DROP ... CASCADE will do, run DROP without CASCADE and read the DETAIL output.) Or you could do BEGIN; DROP ... CASCADE; ROLLBACK. regards, tom lane -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs