From: Tom Lane <tgl@sss.pgh.pa.us>
To: Brad Nicholson <bnichols@ca.afilias.info>
Cc: pgsql-performance@postgresql.org
Subject: Re: Long Running Commits - Not Checkpoints
Date: Thu, 13 Sep 2007 11:10:09 -0400
Message-ID: <15180.1189696209@sss.pgh.pa.us> (raw)
In-Reply-To: <1189695802.8624.25.camel@bnicholson-desktop>
References: <1189692915.8624.22.camel@bnicholson-desktop>
<1189695802.8624.25.camel@bnicholson-desktop>
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
the transaction was doing?
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, bnichols@ca.afilias.info
Subject: Re: Long Running Commits - Not Checkpoints
In-Reply-To: <15180.1189696209@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