X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id B46BDD1C4C4 for ; Wed, 7 Apr 2004 08:54:43 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 55872-05 for ; Wed, 7 Apr 2004 08:54:45 -0300 (ADT) Received: from frodo.hserus.net (frodo.hserus.net [204.74.68.40]) by svr1.postgresql.org (Postfix) with ESMTP id CA8A3D1BC5C for ; Wed, 7 Apr 2004 08:54:41 -0300 (ADT) Received: from concord.pspl.co.in ([202.54.11.72]:61805 helo=ps0499.intranet.pspl.co.in) by frodo.hserus.net with asmtp (Cipher TLSv1:RC4-MD5:128) (Exim 4.31 #0) id 1BBBdk-000IKR-2P by authid with plain for ; Wed, 07 Apr 2004 17:24:44 +0530 From: Shridhar Daithankar Reply-To: shridhar@frodo.hserus.net To: pgsql-performance@postgresql.org Subject: Re: good pc but bad performance,why? Date: Wed, 7 Apr 2004 17:24:41 +0530 User-Agent: KMail/1.6.1 References: <0HVS00G7FMQO35@mail.gthome.com> <1081337381.522.57.camel@lamb.mcmillan.net.nz> <200404071721.43059.shridhar_daithankar@persistent.co.in> In-Reply-To: <200404071721.43059.shridhar_daithankar@persistent.co.in> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200404071724.41860.shridhar@frodo.hserus.net> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/82 X-Sequence-Number: 6382 Sending again bacuse of MUA error.. Chose a wrong address in From..:-( Shridhar On Wednesday 07 April 2004 17:21, Shridhar Daithankar wrote: > 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