pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Brad Nicholson <bnichols@ca.afilias.info>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Long Running Commits - Not Checkpoints
Date: Thu, 13 Sep 2007 11:35:59 -0400
Message-ID: <1189697763.8624.30.camel@bnicholson-desktop> (raw)
In-Reply-To: <15180.1189696209@sss.pgh.pa.us>
References: <1189692915.8624.22.camel@bnicholson-desktop>
	<1189695802.8624.25.camel@bnicholson-desktop>
	<15180.1189696209@sss.pgh.pa.us>

On Thu, 2007-09-13 at 11:10 -0400, Tom Lane wrote:
> Brad Nicholson <bnichols@ca.afilias.info> writes:
> > On Thu, 2007-09-13 at 10:15 -0400, Brad Nicholson wrote:
> >> I'm having a problem with long running commits appearing in my database
> >> logs.  It may be hardware related, as the problem appeared when we moved
> >> the database to a new server connected to a different disk array.
> 
> > More on this - we also have long running commits on installations that
> > do have the wal files on a separate partition.
> 
> What's your definition of "long running commit" --- seconds? milliseconds?
> Exactly what are you measuring?  Can you correlate the problem with what

log_min_duration is set to 150ms

Commits running over that up to 788ms.  Here is what we see in the logs
(with obfuscated dbname, username and IP):

2007-09-13 10:01:49.787 CUT [782426] dbname username 1.2.3.171 LOG:
duration: 224.286 ms  statement: EXECUTE <unnamed>  [PREPARE:  commit]
2007-09-13 10:19:16.373 CUT [737404] dbname username 1.2.3.174 LOG:
duration: 372.545 ms  statement: EXECUTE <unnamed>  [PREPARE:  commit]
2007-09-13 10:19:24.437 CUT [1806498] dbname username 11.2.3.171 LOG:
duration: 351.544 ms  statement: EXECUTE <unnamed>  [PREPARE:  commit]
2007-09-13 10:33:11.204 CUT [962598] dbname username 1.2.3.170 LOG:
duration: 504.057 ms  statement: EXECUTE <unnamed>  [PREPARE:  commit]
2007-09-13 10:40:33.735 CUT [1282104] dbname username 1.2.3.174 LOG:
duration: 250.127 ms  statement: EXECUTE <unnamed>  [PREPARE:  commit]
2007-09-13 10:49:54.752 CUT [1188032] dbname username 1.2.3.170 LOG:
duration: 382.781 ms  statement: EXECUTE <unnamed>  [PREPARE:  commit]
2007-09-13 11:30:43.339 CUT [1589464] dbname username 1.2.3.172 LOG:
duration: 408.463 ms  statement: EXECUTE <unnamed>  [PREPARE:  commit]


-- 
Brad Nicholson  416-673-4106
Database Administrator, Afilias Canada Corp.




view thread (14+ messages)  latest in thread

Message-ID: <1189697763.8624.30.camel@bnicholson-desktop>
Permalink:  ../1189697763.8624.30.camel@bnicholson-desktop/
Also on:    postgresql.org/message-id/1189697763.8624.30.camel@bnicholson-desktop

 · 

reply

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: bnichols@ca.afilias.info, tgl@sss.pgh.pa.us
  Subject: Re: Long Running Commits - Not Checkpoints
  In-Reply-To: <1189697763.8624.30.camel@bnicholson-desktop>

* 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