From: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
To: 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 17:21:43 +0530
Message-ID: <200404071721.43059.shridhar_daithankar@persistent.co.in> (raw)
In-Reply-To: <1081337381.522.57.camel@lamb.mcmillan.net.nz>
References: <0HVS00G7FMQO35@mail.gthome.com>
<1081337381.522.57.camel@lamb.mcmillan.net.nz>
On Wednesday 07 April 2004 16:59, Andrew McMillan wrote:
> One thing I recommend is to use ext2 (or almost anything but ext3).
> 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.
That is not correct assumption. A journalling file system ensures file system
consistency even at a cost of loss of some data. And postgresql can not
guarantee recovery if WAL logs are corrupt. Some months back, there was a
case reported where ext2 corrupted WAL and database. BAckup is only solution
then..
Journalling file systems are usually very close to ext2 in performance, many a
times lot better. With ext2, you are buying a huge risk.
Unless there are good reason, I would not put a database on ext2. Performance
isn't one ofthem..
Shridhar
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: shridhar_daithankar@persistent.co.in, andrew@catalyst.net.nz, hyq@gthome.com
Subject: Re: good pc but bad performance,why?
In-Reply-To: <200404071721.43059.shridhar_daithankar@persistent.co.in>
* 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