From: Giulio Cesare Solaroli <giulio.cesare@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Finalizing commit taking very long
Date: Fri, 26 Oct 2007 14:41:36 +0200
Message-ID: <ff737ac30710260541x4435b5c2lc9d635358efca38d@mail.gmail.com> (raw)
In-Reply-To: <ff737ac30710240725w23128c6l572df131b54341b2@mail.gmail.com>
References: <ff737ac30710240344v4391d2eeq957e91dca6c2f9e0@mail.gmail.com>
<1302.1193231756@sss.pgh.pa.us>
<ff737ac30710240637m39fb0063m466074623d682c38@mail.gmail.com>
<2051.1193234616@sss.pgh.pa.us>
<ff737ac30710240725w23128c6l572df131b54341b2@mail.gmail.com>
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
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: giulio.cesare@gmail.com, tgl@sss.pgh.pa.us
Subject: Re: Finalizing commit taking very long
In-Reply-To: <ff737ac30710260541x4435b5c2lc9d635358efca38d@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox