Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 460DC9FB92E; Wed, 11 Apr 2007 22:40:46 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 02036-09; Wed, 11 Apr 2007 22:40:43 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from serv1.oss.ntt.co.jp (serv1.oss.ntt.co.jp [222.151.198.98]) by postgresql.org (Postfix) with ESMTP id 179EF9FB929; Wed, 11 Apr 2007 22:40:43 -0300 (ADT) Received: from [172.17.1.90] (unknown [172.17.1.90]) by serv1.oss.ntt.co.jp (Postfix) with ESMTP id C16B5104001; Thu, 12 Apr 2007 10:40:40 +0900 (JST) Message-ID: <461D8DF4.1070200@oss.ntt.co.jp> Date: Thu, 12 Apr 2007 10:40:04 +0900 From: Koichi Suzuki User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Tom Lane CC: Simon Riggs , josh@agliodbs.com, pgsql-hackers@postgresql.org, pgsql-patches@postgresql.org Subject: Re: [HACKERS] Full page writes improvement, code update References: <460886E8.6040907@oss.ntt.co.jp> <4609CAC3.7060008@oss.ntt.co.jp> <1175072848.4386.323.camel@silverbirch.site> <200703291145.28574.josh@agliodbs.com> <1175200117.4386.616.camel@silverbirch.site> <460C611E.6090800@oss.ntt.co.jp> <27693.1176226131@sss.pgh.pa.us> <461C3557.6040201@oss.ntt.co.jp> <6050.1176331703@sss.pgh.pa.us> In-Reply-To: <6050.1176331703@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/325 X-Sequence-Number: 1892 The score below was taken based on 8.2 code, not 8.3 code. So I don't think the below measure is introduced only in 8.3 code. Tom Lane wrote: > Koichi Suzuki writes: >> For more information, when checkpoint interval is one hour, the amount >> of the archived log size was as follows: >> cp: 3.1GB >> gzip: 1.5GB >> pg_compresslog: 0.3GB > > The notion that 90% of the WAL could be backup blocks even at very long > checkpoint intervals struck me as excessive, so I went looking for a > reason, and I may have found one. There has been a bug in CVS HEAD > since Feb 8 causing every btree page split record to include a backup > block whether needed or not. If these numbers were taken with recent > 8.3 code, please retest with current HEAD. > > regards, tom lane > -- Koichi Suzuki