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 62C90D1C9EC for ; Tue, 2 Mar 2004 22:16:25 +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 66246-01 for ; Tue, 2 Mar 2004 18:16:21 -0400 (AST) Received: from cmailm5.svr.pol.co.uk (cmailm5.svr.pol.co.uk [195.92.193.21]) by svr1.postgresql.org (Postfix) with ESMTP id 7B170D1C9C2 for ; Tue, 2 Mar 2004 18:16:17 -0400 (AST) Received: from modem-2578.lemur.dialup.pol.co.uk ([217.135.138.18] helo=LaptopDellXP) by cmailm5.svr.pol.co.uk with esmtp (Exim 4.14) id 1AyIBW-0003od-AQ; Tue, 02 Mar 2004 22:16:18 +0000 Reply-To: From: "Simon Riggs" To: , "'Rob Fielding'" , Subject: Re: WAL Optimisation - configuration and usage Date: Tue, 2 Mar 2004 22:16:12 -0000 Organization: 2nd Quadrant Message-ID: <004901c400a3$fb570570$5baa87d9@LaptopDellXP> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal In-Reply-To: <200403011710.07289.josh@agliodbs.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/27 X-Sequence-Number: 5883 >Josh Berkus wrote > >Simon Riggs wrote > > Please set WAL_DEBUG to 1 so we can see a bit more info: thanks. >=20 > I'm pretty sure that WAL_DEBUG requires a compile-time option. In my naivet=E9, I just set and use it. I discovered it in the code, then set it to take advantage. I'm surprised, but you are right, the manual does SAY this requires a compile time option; it is unfortunately not correct. Maybe this was once as you say? If Rob is using 7.2.2 maybe this still applies to him? I don=92t know. Setting wal_debug > 0 in postgresql.conf sets a variable XLOGDEBUG, which although it is all capitals is not in fact a compiler directive, as it looks. This variable is used within xlog.c to output **too much** information to the log. However, it is the only option at present. This prompts me however to consider the idea of having various levels of WAL debug output, or using some kind of log_checkpoint mechanism to better understand what is going on. Best Regards, Simon Riggs