From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: scott.marlowe <scott.marlowe@ihs.com>
Cc: Andrew McMillan <andrew@catalyst.net.nz>
Cc: huang yaqin <hyq@gthome.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: good pc but bad performance,why?
Date: Wed, 7 Apr 2004 21:33:34 -0400 (EDT)
Message-ID: <200404080133.i381XYu13325@candle.pha.pa.us> (raw)
In-Reply-To: <6788.1081387878@sss.pgh.pa.us>
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > scott.marlowe wrote:
> >>> There is no real need (or benefit) from having the database on a
> >>> journalled filesystem - the journalling is only trying to give similar
> >>> sorts of guarantees to what the fsync in PostgreSQL is doing.
> >>
> >> Is this true? I was under the impression that without at least meta-data
> >> journaling postgresql could still be corrupted by power failure.
>
> > It is false. ext2 isn't crash-safe, and PostgreSQL needs an intact file
> > system for WAL recovery.
>
> But it should be okay to set the filesystem to journal only its own
> metadata. There's no need for it to journal file contents.
Can you set ext2 to journal metadata? I didn't know it could do that.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
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: pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, scott.marlowe@ihs.com, andrew@catalyst.net.nz, hyq@gthome.com
Subject: Re: good pc but bad performance,why?
In-Reply-To: <200404080133.i381XYu13325@candle.pha.pa.us>
* 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