From: Joshua D. Drake <jd@commandprompt.com>
To: Dan Langille <dan@langille.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: wal_sync_methods for AIX
Date: Fri, 15 Feb 2008 14:04:53 -0800
Message-ID: <20080215140453.4fafd9b1@commandprompt.com> (raw)
In-Reply-To: <1959485A-0DC4-4EA3-864A-D40A7F8AA094@langille.org>
References: <1959485A-0DC4-4EA3-864A-D40A7F8AA094@langille.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 15 Feb 2008 16:55:45 -0500
Dan Langille <dan@langille.org> wrote:
> Our tests have been on a p550 connected to DS6800 array using pgbench.
>
> One nasty behaviour we have seen is long running commits. Initial
> thoughts connected
> them with checkpoints, but the long running commits do not correlate
> with checkpoints being
> written. Have you seen this behaviour?
Are you sure? What makes you think this? Do you have a high level of
shared buffers? What are your bgwriter settings?
Joshua D. Drake
- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL SPI Liaison | SPI Director | PostgreSQL political pundit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHtgyFATb/zqfZUUQRAv2LAJ41l25YG7PwfgpZtuPD/1aL5I4ZTwCfRGii
LkFFefSDT72qGzY8PxOMXKE=
=0iC3
-----END PGP SIGNATURE-----
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: jd@commandprompt.com, dan@langille.org
Subject: Re: wal_sync_methods for AIX
In-Reply-To: <20080215140453.4fafd9b1@commandprompt.com>
* 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