From: Simon Riggs <simon@2ndquadrant.com>
To: 'Neil Conway' <neilc@samurai.com>
Cc: josh@agliodbs.com
Cc: pgsql-performance@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] WAL Optimisation - configuration and usage
Date: Tue, 9 Mar 2004 20:26:55 -0000
Message-ID: <006601c40614$df319e20$f3bd87d9@LaptopDellXP> (raw)
In-Reply-To: <40466F2C.3050108@samurai.com>
>Neil Conway
> 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.
Yes that's the best proposal. Can I leave that with you?
> > 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.)
Right again. I guess my proposal amounted to quick-and-dirty logging.
I'll think some more.
Best Regards, Simon Riggs
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: simon@2ndquadrant.com, neilc@samurai.com, josh@agliodbs.com, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] WAL Optimisation - configuration and usage
In-Reply-To: <006601c40614$df319e20$f3bd87d9@LaptopDellXP>
* 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