From: Eildert Groeneveld <eildert.groeneveld@fli.bund.de>
To: pgsql-performance@postgresql.org
Subject: list number of entries to be delete in cascading deletes
Date: Tue, 11 Feb 2014 21:54:04 +0100
Message-ID: <1392152044.4823.9.camel@localhost> (raw)
In-Reply-To: <19895.1392133067@sss.pgh.pa.us>
References: <E1WCttM-0006Np-Nj@malur.postgresql.org>
<alpine.DEB.2.02.1402102007580.14849@skaj>
<52F93098.2090002@vmware.com>
<CAGa5y0MNo7r3HdnZMTa+a+W+d14kbRNO-+REyYSMRd9q_XHw1g@mail.gmail.com>
<19895.1392133067@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
Dear All
this probably not the best list to post this question:
I use cascading deletes but would like to first inform the user what she
is about to do.
Something like : explain delete from PANEL where panel_id=21;
-- you are about to delete 32144 records in tables abc aaa wewew
This is clearly something that can be programmed but as all information
is available in the database schema, there should be a generalized
procedure available.
Is there someone who has heard about this problem?
greetings
Eildert
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
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-performance@postgresql.org
Cc: eildert.groeneveld@fli.bund.de
Subject: Re: list number of entries to be delete in cascading deletes
In-Reply-To: <1392152044.4823.9.camel@localhost>
* 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