Re: list number of entries to be delete in cascading deletes - Mailing list pgsql-performance

From Claudio Freire
Subject Re: list number of entries to be delete in cascading deletes
Date
Msg-id CAGTBQpa-hSszXGgN8pQk2SzAE6X9p-_rDrmg_WwSNa7M7cJRog@mail.gmail.com
Whole thread Raw
In response to list number of entries to be delete in cascading deletes  (Eildert Groeneveld <eildert.groeneveld@fli.bund.de>)
Responses Re: list number of entries to be delete in cascading deletes  (Eildert Groeneveld <eildert.groeneveld@fli.bund.de>)
List pgsql-performance
On Tue, Feb 11, 2014 at 5:54 PM, Eildert Groeneveld
<eildert.groeneveld@fli.bund.de> wrote:
> 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.

Granted, this is somewhat ugly, but you could issue the delete, note
down the rowcount, and rollback.


pgsql-performance by date:

Previous
From: Eildert Groeneveld
Date:
Subject: list number of entries to be delete in cascading deletes
Next
From: Jeff Janes
Date:
Subject: Re: Bloated tables and why is vacuum full the only option