Message-ID: <1392152044.4823.9.camel@localhost>
Subject: list number of entries to be delete in cascading deletes
From: Eildert Groeneveld <eildert.groeneveld@fli.bund.de>
Reply-To: eildert.groeneveld@fli.bund.de
To: pgsql-performance@postgresql.org
Date: Tue, 11 Feb 2014 21:54:04 +0100
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>
Organization: FLI
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

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