Re: Finalizing commit taking very long - Mailing list pgsql-performance

From Giulio Cesare Solaroli
Subject Re: Finalizing commit taking very long
Date
Msg-id ff737ac30710260541x4435b5c2lc9d635358efca38d@mail.gmail.com
Whole thread Raw
In response to Re: Finalizing commit taking very long  ("Giulio Cesare Solaroli" <giulio.cesare@gmail.com>)
List pgsql-performance
Hello Tom,

I can confirm that adding the indexes used by the deferred constraint
triggers solved the issue.

Thank you very much for your suggestions.

Best regards,

Giulio Cesare


On 10/24/07, Giulio Cesare Solaroli <giulio.cesare@gmail.com> wrote:
> On 10/24/07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > "Giulio Cesare Solaroli" <giulio.cesare@gmail.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
>

pgsql-performance by date:

Previous
From: Gregory Stark
Date:
Subject: Re: [HACKERS] 8.3beta1 testing on Solaris
Next
From: Jean-David Beyer
Date:
Subject: Re: Bunching "transactions"