From: Josh Berkus <josh@agliodbs.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org, Robert Treat <xzilla@users.sourceforge.net>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: Greg Smith <gsmith@gregsmith.com>
Cc: Andreas Pflug <pgadmin@pse-consulting.de>
Cc: Decibel! <decibel@decibel.org>
Subject: Re: Overhauling GUCS
Date: Wed, 11 Jun 2008 09:37:22 -0700
Message-ID: <484FFF42.7000408@agliodbs.com> (raw)
In-Reply-To: <21875.1213122184@sss.pgh.pa.us>
References: <48409D1E.3070208@agliodbs.com>
<200806061624.29105.xzilla@users.sourceforge.net>
<200806100937.38124.josh@agliodbs.com>
<200806100949.17918.josh@agliodbs.com>
<21875.1213122184@sss.pgh.pa.us>
Tom Lane wrote:
> Josh Berkus <josh@agliodbs.com> writes:
>> Oh, and wal_buffers, the default for which we should just change if it
>> weren't for SHMMAX.
>
> Uh, why? On a workload of mostly small transactions, what value is
> there in lots of wal_buffers?
Actually, it's also useful for any workload with many connections. Any
time you have high throughput, really. We've seen this on DBT2,
SpecJAppserver and iGen.
--Josh
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-hackers@postgresql.org
Cc: josh@agliodbs.com, tgl@sss.pgh.pa.us, xzilla@users.sourceforge.net, peter_e@gmx.net, gsmith@gregsmith.com, pgadmin@pse-consulting.de, decibel@decibel.org
Subject: Re: Overhauling GUCS
In-Reply-To: <484FFF42.7000408@agliodbs.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