From: db@zigo.dhs.org
To: Brad Nicholson <bnichols@ca.afilias.info>
Cc: pgsql-performance@postgresql.org
Subject: Re: Long Running Commits - Not Checkpoints
Date: Fri, 14 Sep 2007 13:31:45 +0200 (CEST)
Message-ID: <43618.192.121.104.48.1189769505.squirrel@zigo.dhs.org> (raw)
In-Reply-To: <1189692915.8624.22.camel@bnicholson-desktop>
References: <1189692915.8624.22.camel@bnicholson-desktop>
> 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. The
> disk array is a lower class array, but still more than powerful enough
> to handle the IO requirements. One big difference though is that the
> old array had 16 GB of cache, the new one has 4 GB.
Maybe the old disk array had battery backed up ram that was used as a
write cache and the new only has read cache? Without battery backed up ram
(or flash or whatever) then a commit need to flush data down onto the
pysical disk.
/Dennis
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: db@zigo.dhs.org, bnichols@ca.afilias.info
Subject: Re: Long Running Commits - Not Checkpoints
In-Reply-To: <43618.192.121.104.48.1189769505.squirrel@zigo.dhs.org>
* 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