Re: Help with duration of statement: EXECUTE <unnamed> [PREPARE: COMMIT]

From: Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Eric Comeau <ecomeau(at)signiant(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Help with duration of statement: EXECUTE <unnamed> [PREPARE: COMMIT]
Date: 2010-10-18 14:25:17
Message-ID: 4CBC58CD.9010906@vmsinfo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Alvaro Herrera 2010-10-18 14:44:53 Re: No hash join across partitioned tables?
Previous Message Tom Lane 2010-10-18 14:13:53 Re: Help with duration of statement: EXECUTE <unnamed> [PREPARE: COMMIT]