X-Original-To: pgsql-hackers-pitr-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id E6E9ED1CB0F; Wed, 3 Mar 2004 23:49:58 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 36839-04; Wed, 3 Mar 2004 19:50:04 -0400 (AST) Received: from bob.samurai.com (bob.samurai.com [205.207.28.75]) by svr1.postgresql.org (Postfix) with ESMTP id BCCC5D1CA52; Wed, 3 Mar 2004 19:49:55 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by bob.samurai.com (Postfix) with ESMTP id C636E1D8F; Wed, 3 Mar 2004 18:50:03 -0500 (EST) Received: from bob.samurai.com ([127.0.0.1]) by localhost (bob.samurai.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 44206-01-3; Wed, 3 Mar 2004 18:50:03 -0500 (EST) Received: from samurai.com (d226-89-59.home.cgocable.net [24.226.89.59]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by bob.samurai.com (Postfix) with ESMTP id 903ED1D66; Wed, 3 Mar 2004 18:50:02 -0500 (EST) Message-ID: <40466F2C.3050108@samurai.com> Date: Wed, 03 Mar 2004 18:50:04 -0500 From: Neil Conway User-Agent: Mozilla Thunderbird 0.5 (X11/20040221) X-Accept-Language: en-us, en MIME-Version: 1.0 To: simon@2ndquadrant.com Cc: josh@agliodbs.com, 'Rob Fielding' , pgsql-performance@postgresql.org, pgsql-hackers-pitr@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: [PERFORM] WAL Optimisation - configuration and usage References: <006801c40168$1db208d0$5baa87d9@LaptopDellXP> In-Reply-To: <006801c40168$1db208d0$5baa87d9@LaptopDellXP> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mailbox.samurai.com X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/3 X-Sequence-Number: 27 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