From: Ian Westmacott <ianw@intellivid.com>
To: Thomas F. O'Connell <tfo@sitening.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: wal_buffers
Date: Thu, 06 Oct 2005 08:56:31 -0400
Message-ID: <1128603390.18319.16.camel@spectre.intellivid.com> (raw)
In-Reply-To: <C140F925-0D7D-41B4-873A-6C81C0D3D307@sitening.com>
References: <1128518624.15795.28.camel@spectre.intellivid.com>
<C140F925-0D7D-41B4-873A-6C81C0D3D307@sitening.com>
On Thu, 2005-10-06 at 02:39, Thomas F. O'Connell wrote:
> The WAL Configuration chapter (25.2) has a pretty good discussion of
> how wal_buffers is used:
>
> http://www.postgresql.org/docs/8.0/static/wal-configuration.html
>
> You might also take a look at Josh Berkus' recent testing on this
> setting:
>
> http://www.powerpostgresql.com/
Thanks; I'd seen the documentation, but not Josh Berkus'
testing.
For my part, I don't have a large number of concurrent
connections, only one. But it is doing large writes,
and XLogInsert is number 2 on the profile (with
LWLockAcquire and LWLockRelease close behind). I suppose
that is expected, but lead by the documentation I wanted
to make sure XLogInsert always had some buffer space to
play with.
--Ian
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: ianw@intellivid.com, tfo@sitening.com
Subject: Re: wal_buffers
In-Reply-To: <1128603390.18319.16.camel@spectre.intellivid.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