X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 07D34D89CA for ; Thu, 10 Nov 2005 11:52:35 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 57127-02 for ; Thu, 10 Nov 2005 15:52:31 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from koolancexeon.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by svr1.postgresql.org (Postfix) with ESMTP id 85DB2D7C91 for ; Thu, 10 Nov 2005 11:52:33 -0400 (AST) Received: mail.g2switchworks.com 10.10.1.8 from 10.10.1.37 10.10.1.37 via HTTP with MS-WebStorage 6.5.6944 Received: from state.g2switchworks.com by mail.g2switchworks.com; 10 Nov 2005 09:52:38 -0600 Subject: Re: WAL sync behaviour From: Scott Marlowe To: Michael Stone Cc: pgsql-performance@postgresql.org In-Reply-To: <20051110144309.GO9905@mathom.us> References: <20051110133241.GA4031@uio.no> <437355C6.4030604@archonet.com> <20051110142535.GA4530@uio.no> <20051110144309.GO9905@mathom.us> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1131637958.3554.75.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Thu, 10 Nov 2005 09:52:38 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.007 required=5 tests=[AWL=0.006, UNPARSEABLE_RELAY=0.001] X-Spam-Score: 0.007 X-Spam-Level: X-Archive-Number: 200511/181 X-Sequence-Number: 15438 On Thu, 2005-11-10 at 08:43, Michael Stone wrote: > On Thu, Nov 10, 2005 at 03:25:35PM +0100, Steinar H. Gunderson wrote: > >Ah, yes, I forgot -- it's ext3. We're considering simply moving the WAL onto > >a separate partition (with data=writeback and noatime) if that can help us > >any. > > There's no reason to use a journaled filesystem for the wal. Use ext2 in > preference to ext3. Not from what I understood. Ext2 can't guarantee that your data will even be there in any form after a crash. I believe only metadata journaling is needed though.