From: | "Giulio Cesare Solaroli" <giulio(dot)cesare(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Finalizing commit taking very long |
Date: | 2007-10-24 14:25:53 |
Message-ID: | ff737ac30710240725w23128c6l572df131b54341b2@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 10/24/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Giulio Cesare Solaroli" <giulio(dot)cesare(at)gmail(dot)com> writes:
> > How can I try to isolate the trigger taking so long, in oder to
> > understand which is/are the missing index(es)?
>
> Try SET CONSTRAINTS ALL IMMEDIATE and then EXPLAIN ANALYZE the
> delete. This should cause all the triggers to run within the
> scope of the EXPLAIN ANALYZE, and you'll be able to see which
> one(s) are slow. (This assumes you're running a recent release
> of PG; I think EXPLAIN shows trigger times since 8.1 or so.)
I was thinking about something similar after writing the last message.
Thank you very much for your attention!!
Giulio Cesare
From | Date | Subject | |
---|---|---|---|
Next Message | Sven Geisler | 2007-10-24 14:33:10 | Re: multiple apaches against single postgres database |
Previous Message | Tom Lane | 2007-10-24 14:03:36 | Re: Finalizing commit taking very long |