From: Jeffrey D. Brower <jeff@pointhere.net>
To: josh@agliodbs.com
To: Andreas Kostyrka <andreas@mtg.co.at>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: pgsql-performance@postgresql.org
Cc: Shankar K <shan0075@yahoo.com>
Cc: eric soroos <eric-psql@soroos.net>
Subject: Re: ext3 filesystem / linux 7.3
Date: Wed, 2 Apr 2003 19:29:57 -0500
Message-ID: <0a8001c2f978$28959a80$0b02a8c0@pointhere.net> (raw)
References: <26287373.1162931668@[4.42.179.151]>
<1049298455.21669.333.camel@andi-lap>
<0a6f01c2f93a$6907bf50$0b02a8c0@pointhere.net>
<200304021205.30075.josh@agliodbs.com>
Thanks for that Josh.
I had previously understood that ext3 was a bad thing with PostgreSQL and I
went way above and beyond to create it on an Ext2 filesystem (the only one
on the server) and mount that.
Should I undo that work and go back to Ext3?
Jeff
----- Original Message -----
From: "Josh Berkus" <josh@agliodbs.com>
To: "Jeffrey D. Brower" <jeff@pointhere.net>; "Andreas Kostyrka"
<andreas@mtg.co.at>
Cc: "Bruce Momjian" <pgman@candle.pha.pa.us>;
<pgsql-performance@postgresql.org>; "Shankar K" <shan0075@yahoo.com>; "eric
soroos" <eric-psql@soroos.net>
Sent: Wednesday, April 02, 2003 3:05 PM
Subject: Re: [PERFORM] ext3 filesystem / linux 7.3
> Jeff,
>
> > How all of that works WITH and/or AGAINST PostgreSQL and what metadata
> > REALLY means is my bottom line quandary. Obviously that is where
finding
> > the warm and fuzzy place between speed and safety is found.
>
> For your $PGDATA directory, your only need for filesystem journaling is to
> prevent a painful fsck process on an unexpected power-out. You are not,
as a
> rule, terribly concerned with journaling the data as PostgreSQL already
> provides some data recovery protection through WAL.
>
> As a result, on my one server where I have to use Ext3 (I use Reiser on
most
> machines, and have never had a problem except for one disaster when
upgrading
> Reiser versions), the $PGDATA is mounted "noatime,data=writeback"
>
> (BTW, I found that combining "data=writeback" with Linux LVM on RedHat 8.0
> resulted in system-fatal mounting errors. Anyone else have this
problem?)
>
> Of course, if you have a machine with a $60,000 disk array and disk I/O is
> unlimited, then maybe you want to enable data=journal just for the
protection
> against corruption of the WAL and clog files.
>
> --
> -Josh Berkus
> Aglio Database Solutions
> San Francisco
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: jeff@pointhere.net, josh@agliodbs.com, andreas@mtg.co.at, pgman@candle.pha.pa.us, shan0075@yahoo.com, eric-psql@soroos.net
Subject: Re: ext3 filesystem / linux 7.3
In-Reply-To: <0a8001c2f978$28959a80$0b02a8c0@pointhere.net>
References: <26287373.1162931668@[4.42.179.151]> <1049298455.21669.333.camel@andi-lap> <0a6f01c2f93a$6907bf50$0b02a8c0@pointhere.net> <200304021205.30075.josh@agliodbs.com> <0a8001c2f978$28959a80$0b02a8c0@pointhere.net>
* 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