From: Mladen Gogala <mladen.gogala@vmsinfo.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
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 10:25:17 -0400
Message-ID: <4CBC58CD.9010906@vmsinfo.com> (raw)
In-Reply-To: <18890.1287411233@sss.pgh.pa.us>
References: <i9c60b$ifv$1@news.hub.org>
<18890.1287411233@sss.pgh.pa.us>
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?
--
Mladen Gogala
Sr. Oracle DBA
1500 Broadway
New York, NY 10036
(212) 329-5251
http://www.vmsinfo.com
The Leader in Integrated Media Intelligence Solutions
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: mladen.gogala@vmsinfo.com, tgl@sss.pgh.pa.us, ecomeau@signiant.com
Subject: Re: Help with duration of statement: EXECUTE <unnamed> [PREPARE: COMMIT]
In-Reply-To: <4CBC58CD.9010906@vmsinfo.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