Re: Help with duration of statement: EXECUTE [PREPARE: COMMIT] - Mailing list pgsql-performance

From Tom Lane
Subject Re: Help with duration of statement: EXECUTE [PREPARE: COMMIT]
Date
Msg-id 19782.1287414135@sss.pgh.pa.us
Whole thread Raw
In response to Re: Help with duration of statement: EXECUTE [PREPARE: COMMIT]  (Mladen Gogala <mladen.gogala@vmsinfo.com>)
Responses Re: Help with duration of statement: EXECUTE [PREPARE: COMMIT]
List pgsql-performance
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

pgsql-performance by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: No hash join across partitioned tables?
Next
From: Josh Kupershmidt
Date:
Subject: Re: how to get the total number of records in report