From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Michael Stone <mstone+postgres@mathom.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: WAL sync behaviour
Date: Thu, 10 Nov 2005 09:52:38 -0600
Message-ID: <1131637958.3554.75.camel@state.g2switchworks.com> (raw)
In-Reply-To: <20051110144309.GO9905@mathom.us>
References: <20051110133241.GA4031@uio.no>
<437355C6.4030604@archonet.com>
<20051110142535.GA4530@uio.no>
<20051110144309.GO9905@mathom.us>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: smarlowe@g2switchworks.com, mstone+postgres@mathom.us
Subject: Re: WAL sync behaviour
In-Reply-To: <1131637958.3554.75.camel@state.g2switchworks.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox