From: Tom Lane <tgl@sss.pgh.pa.us>
To: Giulio Cesare Solaroli <giulio.cesare@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Finalizing commit taking very long
Date: Wed, 24 Oct 2007 09:15:56 -0400
Message-ID: <1302.1193231756@sss.pgh.pa.us> (raw)
In-Reply-To: <ff737ac30710240344v4391d2eeq957e91dca6c2f9e0@mail.gmail.com>
References: <ff737ac30710240344v4391d2eeq957e91dca6c2f9e0@mail.gmail.com>
"Giulio Cesare Solaroli" <giulio.cesare@gmail.com> writes:
> As you may notice, the commit phase takes almost 2 full minutes. :-(
Yow. It's hard to believe that the actual commit (ie, flushing the
commit record to WAL) could take more than a fraction of a second.
I'm thinking there must be a pile of pre-commit work to do, like a
lot of deferred triggers. Do you use deferred foreign keys?
If so, the most likely bet is that the DELETE is triggering a lot
of deferred FK checks, and these are slow for some reason (maybe
another missing index).
regards, tom lane
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: tgl@sss.pgh.pa.us, giulio.cesare@gmail.com
Subject: Re: Finalizing commit taking very long
In-Reply-To: <1302.1193231756@sss.pgh.pa.us>
* 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