On Mon, Feb 27, 2012 at 9:35 PM, Tatsuo Ishii <is...@postgresql.org> wrote:

> Are you suggesting log_statement? I don't think it's a solution by
> following reasons:
> 1) it's slow to enable that on busy systems
> 2) tables affected by cascading delete/update/drop is not logged in
>   PostgreSQL log
Would looking into currently held locks help ? You might get some false
positive because the transaction may have acquired a lock, but did not do
any modification. But if you can live with that, it might be worth


Pavan Deolasee
EnterpriseDB     http://www.enterprisedb.com

Reply via email to