From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mladen Gogala <mladen.gogala@vmsinfo.com>
Cc: Eric Comeau <ecomeau@signiant.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Help with duration of statement: EXECUTE <unnamed> [PREPARE: COMMIT]
Date: Mon, 18 Oct 2010 11:02:15 -0400
Message-ID: <19782.1287414135@sss.pgh.pa.us> (raw)
In-Reply-To: <4CBC58CD.9010906@vmsinfo.com>
References: <i9c60b$ifv$1@news.hub.org>
<18890.1287411233@sss.pgh.pa.us>
<4CBC58CD.9010906@vmsinfo.com>
Mladen Gogala <mladen.gogala@vmsinfo.com> writes:
> Tom Lane wrote:
>> My guess would be overstressed disk subsystem. A COMMIT doesn't require
>> much except fsync'ing the commit WAL record down to disk ...
> Doesn't the "commit" statement also release all the locks held by the
> transaction?
Yeah, and there's a nontrivial amount of other cleanup too, but it all
amounts to just changes in in-memory data structures. I don't see that
taking five seconds, especially not if commits of similar transactions
usually take much less than that.
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, mladen.gogala@vmsinfo.com, ecomeau@signiant.com
Subject: Re: Help with duration of statement: EXECUTE <unnamed> [PREPARE: COMMIT]
In-Reply-To: <19782.1287414135@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