From: Neil Conway <neilc@samurai.com>
To: simon@2ndquadrant.com
Cc: josh@agliodbs.com, 'Rob Fielding' <rob@dsvr.net>
Cc: pgsql-performance@postgresql.org
Cc: pgsql-hackers-pitr@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: [PERFORM] WAL Optimisation - configuration and usage
Date: Wed, 03 Mar 2004 18:50:04 -0500
Message-ID: <40466F2C.3050108@samurai.com> (raw)
In-Reply-To: <006801c40168$1db208d0$5baa87d9@LaptopDellXP>
References: <006801c40168$1db208d0$5baa87d9@LaptopDellXP>
Simon Riggs wrote:
> On the other hand, I was just about to change the wal_debug behaviour to
> allow better debugging of PITR features as they're added.
That's a development activity. Enabling the WAL_DEBUG #ifdef by
default during the 7.5 development cycle would be uncontroversial, I
think.
> I think it is very important to be able to put the system fairly
> easily into debug mode
It is? Why would this be useful for non-development activities?
(It may well be the case that we ought to report more or better
information about the status of the WAL subsystem; but WAL_DEBUG is
surely not the right mechanism for emitting information intended for
an administrator.)
-Neil
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: neilc@samurai.com, simon@2ndquadrant.com, rob@dsvr.net, pgsql-hackers-pitr@postgresql.org, pgsql-hackers@postgresql.org
Subject: Re: [PERFORM] WAL Optimisation - configuration and usage
In-Reply-To: <40466F2C.3050108@samurai.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