From: mark@mark.mielke.cc
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jim C. Nasby <jnasby@pervasive.com>
Cc: Steve Poe <steve.poe@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgresql Performance on an HP DL385 and
Date: Tue, 15 Aug 2006 16:29:48 -0400
Message-ID: <20060815202948.GC13695@mark.mielke.cc> (raw)
In-Reply-To: <19783.1155672317@sss.pgh.pa.us>
References: <20060809210539.GR40481@pervasive.com>
<1155180553.13315.0.camel@amd64-gentoo-laptop>
<20060810110935.GF2900@mathom.us>
<20060814153841.GF27928@pervasive.com>
<721b21dc0608140851v2332cdf9g59808004c983540f@mail.gmail.com>
<20060814170545.GG27928@pervasive.com>
<20060814170902.GN2900@mathom.us>
<20060815162926.GS27928@pervasive.com>
<20060815183147.GB12834@mark.mielke.cc>
<19783.1155672317@sss.pgh.pa.us>
On Tue, Aug 15, 2006 at 04:05:17PM -0400, Tom Lane wrote:
> mark@mark.mielke.cc writes:
> > I've been worrying about this myself, and my current conclusion is that
> > ext2 is bad because: a) fsck, and b) data can be lost or corrupted, which
> > could lead to the need to trash the xlog.
> > Even ext3 in writeback mode allows for the indirect blocks to be updated
> > without the data underneath, allowing for blocks to point to random data,
> > or worse, previous apparently sane data (especially if the data is from
> > a drive only used for xlog - the chance is high that a block might look
> > partially valid?).
> At least for xlog, this worrying is misguided, because we zero and fsync
> a WAL file before we ever put any valuable data into it. Unless the
> filesystem is lying through its teeth about having done an fsync, there
> should be no metadata changes happening for an active WAL file (other
> than mtime of course).
Hmmm... I may have missed a post about this in the archive.
WAL file is never appended - only re-written?
If so, then I'm wrong, and ext2 is fine. The requirement is that no
file system structures change as a result of any writes that
PostgreSQL does. If no file system structures change, then I take
everything back as uninformed.
Please confirm whichever. :-)
Cheers,
mark
--
mark@mielke.cc / markm@ncf.ca / markm@nortel.com __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ |
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada
One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...
http://mark.mielke.cc/
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: mark@mark.mielke.cc, tgl@sss.pgh.pa.us, jnasby@pervasive.com, steve.poe@gmail.com
Subject: Re: Postgresql Performance on an HP DL385 and
In-Reply-To: <20060815202948.GC13695@mark.mielke.cc>
* 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