Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 51FE36337B6 for ; Fri, 26 Mar 2010 11:00:50 -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 46215-08 for ; Fri, 26 Mar 2010 14:00:39 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-gy0-f174.google.com (mail-gy0-f174.google.com [209.85.160.174]) by mail.postgresql.org (Postfix) with ESMTP id DE163633755 for ; Fri, 26 Mar 2010 11:00:39 -0300 (ADT) Received: by gyg13 with SMTP id 13so205733gyg.19 for ; Fri, 26 Mar 2010 07:00:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=PJ0U+zQXGkx7Yg0QtH/shELdu8QXMmoNArqu4MZRCUE=; b=eLM+L613zisnsCyLr/53npegIyGgNumGvMOuqRxz35FfRvwonhY+QU5vG/B4ugzOJY Ln+HcJHzOuVQDoR+G9irPjXbuqTUaWEK8SFCD7EvHR8QTjUzjzSe5z7bUCsVcpa9mvpt 1HxiIlPK5srmdm2P+70t5ENi0PjwmuZKwcEIc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=QIyOVmqwCuj/fl0s9ecQAGs5589ysYN4rnk/ZpUpE6/fg5JyL5tefc15FGS/m3vx09 9sDwH8eQ1qit7F6wuVO3YvLK1DZTsSGkDBhaHTksK4uCNAsCFvMuzhwljgPS4rL8OsDG gGtD1YgZDgo77bTyHG1Z9hoPpHK3n51pQjlYc= MIME-Version: 1.0 Received: by 10.151.51.20 with HTTP; Fri, 26 Mar 2010 07:00:38 -0700 (PDT) In-Reply-To: References: <645d9d71003250801o246439a0j93c7b568786e98de@mail.gmail.com> <3073cc9b1003251015x590e962ata59dadbb58b42ce5@mail.gmail.com> <645d9d71003252019u6f01a513x7876c1a97b448dea@mail.gmail.com> Date: Fri, 26 Mar 2010 08:00:38 -0600 Received: by 10.151.87.10 with SMTP id p10mr1411826ybl.85.1269612038125; Fri, 26 Mar 2010 07:00:38 -0700 (PDT) Message-ID: Subject: Re: Why Wal_buffer is 64KB From: Scott Marlowe To: Pierre C Cc: Tadipathri Raghu , Jaime Casanova , pgsql-performance@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201003/337 X-Sequence-Number: 38162 On Fri, Mar 26, 2010 at 7:43 AM, Pierre C wrote: > >> 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. There are situations where it's ok, when all the data are reproduceable from other sources, etc. for instance I have a reporting server that is a slony slave that runs with fsync off. If it does crash and I can recreate the node in an hour or so and be back online. With fsync off the machine is too slow to do its job, and it's not the primary repo of the real data, so it's ok there.