From: Josh Berkus <josh@agliodbs.com>
To: Neil Conway <neilc@samurai.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: WAL Optimisation - configuration and usage
Date: Wed, 3 Mar 2004 10:58:20 -0800
Message-ID: <200403031058.20934.josh@agliodbs.com> (raw)
In-Reply-To: <40452047.6030501@samurai.com>
References: <004901c400a3$fb570570$5baa87d9@LaptopDellXP>
<40452047.6030501@samurai.com>
Neil,
> Actually, the manual is correct: in 7.4 and earlier releases, enabling
> wal_debug can be done without also setting a compile-time #ifdef. As
> of current CVS HEAD, the WAL_DEBUG #ifdef must be defined before this
> variable is available.
Hmmm. I was told that it was this way for 7.4 as well; that's why it's in
the docs that way.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, neilc@samurai.com
Subject: Re: WAL Optimisation - configuration and usage
In-Reply-To: <200403031058.20934.josh@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