X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 0FD8ED1DB34; Tue, 9 Mar 2004 20:27:13 +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 50390-07; Tue, 9 Mar 2004 16:27:11 -0400 (AST) Received: from cmailg6.svr.pol.co.uk (cmailg6.svr.pol.co.uk [195.92.195.176]) by svr1.postgresql.org (Postfix) with ESMTP id 04B9DD1DAFB; Tue, 9 Mar 2004 16:27:10 -0400 (AST) Received: from modem-3858.rhino.dialup.pol.co.uk ([62.137.111.18] helo=LaptopDellXP) by cmailg6.svr.pol.co.uk with esmtp (Exim 4.14) id 1B0noe-0008Sw-Nz; Tue, 09 Mar 2004 20:27:05 +0000 Reply-To: From: "Simon Riggs" To: "'Neil Conway'" Cc: , , Subject: Re: [HACKERS] WAL Optimisation - configuration and usage Date: Tue, 9 Mar 2004 20:26:55 -0000 Organization: 2nd Quadrant Message-ID: <006601c40614$df319e20$f3bd87d9@LaptopDellXP> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <40466F2C.3050108@samurai.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300 Importance: Normal X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/110 X-Sequence-Number: 5966 >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