Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 866F91337B7D for ; Tue, 18 Jan 2011 07:51:06 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 74306-01 for ; Tue, 18 Jan 2011 11:51:00 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mail.postgresql.org (Postfix) with ESMTP id 8F9311337B64 for ; Tue, 18 Jan 2011 07:50:58 -0400 (AST) Received: from [192.168.1.6] (mail.highperformancepostgresql.com [71.179.240.8]) by mrelayeu.kundenserver.de (node=mreu1) with ESMTP (Nemesis) id 0Mh8jt-1Ps08V0x5l-00Mzo7; Tue, 18 Jan 2011 12:50:55 +0100 Message-ID: <4D357E9C.6080206@2ndquadrant.com> Date: Tue, 18 Jan 2011 06:50:52 -0500 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Fujii Masao CC: Tom Lane , Robert Haas , Magnus Hagander , pgsql-hackers@postgresql.org Subject: Re: auto-sizing wal_buffers References: <20767.1294964709@sss.pgh.pa.us> <4D314406.3000703@2ndquadrant.com> <4D31D0E4.9000108@2ndquadrant.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:LShK95MuydqJtMMS1YmnmE9lAS2VWONDZiEPeK9g/0E DaQVR3r8RV0yicKaO2Q/SR33eO54lxu1C8bnG8lCFlP3jU29BF PpcP1vOapeF4rwxJ+jpS9QHM+WPpYCEye+BD8W3p13z6hC/Mxb 5t77R9kEP3V3mW+k1pEeGQ9l3tMqo8kn5gGfbKU8gYqsZpet3p gdvqsMqYx2dQn16PAfKrmHaxKDPBbCW+B4xRlku1D4= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201101/1641 X-Sequence-Number: 179478 Fujii Masao wrote: > +/* Minimum setting used for a lower bound on wal_buffers */ > +#define XLOG_BUFFER_MIN 4 > > Why didn't you use XLOG_BUFFER_MIN instead of XLOGbuffersMin? > XLOG_BUFFER_MIN is not used anywhere for now. > That's a typo; will fix. > + if (XLOGbuffers < (XLOGbuffersMin * 2)) > + XLOGbuffers = XLOGbuffersMin * 2; > + } > > Why is the minimum value 64kB only when wal_buffers is set to > -1? This seems confusing for users. > That's because the current default on older versions is 64kB. Since the automatic selection is going to be the new default, I hope, I don't want it to be possible it will pick a number smaller than the default of older versions. So the automatic lower limit is 64kB, while the actual manually set lower limit remains 32kB, as before. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us "PostgreSQL 9.0 High Performance": http://www.2ndQuadrant.com/books