Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 06202632805 for ; Fri, 26 Mar 2010 10:49:27 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 44519-07 for ; Fri, 26 Mar 2010 13:49:16 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from 30.mail-out.ovh.net (30.mail-out.ovh.net [213.186.62.213]) by mail.postgresql.org (Postfix) with SMTP id 31A83633657 for ; Fri, 26 Mar 2010 10:49:16 -0300 (ADT) Received: (qmail 19014 invoked by uid 503); 26 Mar 2010 13:58:11 -0000 Received: from b7.ovh.net (HELO mail637.ha.ovh.net) (213.186.33.57) by 30.mail-out.ovh.net with SMTP; 26 Mar 2010 13:58:11 -0000 Received: from b0.ovh.net (HELO queueout) (213.186.33.50) by b0.ovh.net with SMTP; 26 Mar 2010 13:49:56 -0000 Received: from par69-8-88-161-102-87.fbx.proxad.net (HELO localhost) (lists%peufeu.com@88.161.102.87) by ns0.ovh.net with SMTP; 26 Mar 2010 13:49:55 -0000 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Tadipathri Raghu" Cc: "Jaime Casanova" , pgsql-performance@postgresql.org Subject: Re: Why Wal_buffer is 64KB References: <645d9d71003250801o246439a0j93c7b568786e98de@mail.gmail.com> <3073cc9b1003251015x590e962ata59dadbb58b42ce5@mail.gmail.com> <645d9d71003252019u6f01a513x7876c1a97b448dea@mail.gmail.com> Date: Fri, 26 Mar 2010 14:43:45 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Pierre C" Message-ID: In-Reply-To: <645d9d71003252019u6f01a513x7876c1a97b448dea@mail.gmail.com> User-Agent: Opera Mail/10.10 (Linux) X-Ovh-Tracer-Id: 13511643307754456792 X-Ovh-Remote: 88.161.102.87 (par69-8-88-161-102-87.fbx.proxad.net) X-Ovh-Local: 213.186.33.20 (ns0.ovh.net) X-Spam-Check: DONE|U 0.5/N X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=-10 required=5 tests=BAYES_50=0.001 X-Spam-Level: X-Archive-Number: 201003/336 X-Sequence-Number: 38161 > After fsync/syncronous_commit off Do not use fsync off, it is not safe. Who cares about the performance of fsync=off, when in practice you'd never use it with real data. synchronnous_commit=off is fine for some applications, though. More info is needed about your configuration (hardware, drives, memory, etc).