Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 0BC042E007C for ; Sat, 19 Apr 2008 12:01:54 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 44306-10 for ; Sat, 19 Apr 2008 12:01:50 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from ptb-relay01.plus.net (ptb-relay01.plus.net [212.159.14.212]) by developer.postgresql.org (Postfix) with ESMTP id 20D6E2E0062 for ; Sat, 19 Apr 2008 12:01:49 -0300 (ADT) Received: from [80.229.150.39] (helo=mansionfamily.plus.com) by ptb-relay01.plus.net with esmtp (Exim) id 1JnEZW-0002Gn-W3 for pgsql-performance@postgresql.org; Sat, 19 Apr 2008 16:01:47 +0100 Received: from [192.168.0.87] ([192.168.0.87]:3636) by mansionfamily.plus.com with [XMail 1.22 ESMTP Server] id for from ; Sat, 19 Apr 2008 16:07:11 +0100 Message-ID: <480A0A5D.8060604@mansionfamily.plus.com> Date: Sat, 19 Apr 2008 16:06:05 +0100 From: James Mansion Organization: MsgWare User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: Greg Smith CC: Marinos Yannikos , pgsql-performance@postgresql.org Subject: Re: Background writer underemphasized ... References: <480619CA.2080904@geizhals.at> <48079AED.8090906@geizhals.at> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Plusnet-Relay: 56ce708d40e401b250e1fa4df3ced6c5 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/285 X-Sequence-Number: 29778 Greg Smith wrote: > Using the background writer more assures that the cache on the > controller is going to be written to aggressively, so it may be > somewhat filled already come checkpoint time. If you leave the writer > off, when the checkpoint comes you're much more likely to have the > full 2GB available to absorb a large block of writes. But isn't it the case that while using background writer might result in *slightly* more data to write (since data that is updated several times might actually be sent several times), the total amount of data in both cases is much the same? And if the buffer backed up in the BGW case, wouldn't it also back up (more?) if the writes are deferred? And in fact by sending earlier, the real bottleneck (the disks) could have been getting on with it and staring their IO earlier? Can you explian your reasoning a bit more? James