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 E0641D1D066 for ; Wed, 7 Apr 2004 08:51:50 -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 51172-08 for ; Wed, 7 Apr 2004 08:51:50 -0300 (ADT) Received: from smtp.pspl.co.in (unknown [202.54.11.65]) by svr1.postgresql.org (Postfix) with ESMTP id 116B2D1C50B for ; Wed, 7 Apr 2004 08:51:45 -0300 (ADT) Received: (from root@localhost) by smtp.pspl.co.in (8.12.9/8.12.9) id i37BpuoO026414 for ; Wed, 7 Apr 2004 17:21:56 +0530 X-Scanned: XAM28854 Scanned by XAMIME Received: from ps0499.intranet.pspl.co.in (PS0499.intranet.pspl.co.in [192.168.10.204]) (authenticated bits=0) by persistent.co.in (8.12.9/8.12.9) with ESMTP id i37Bpr26026372; Wed, 7 Apr 2004 17:21:54 +0530 From: Shridhar Daithankar To: Andrew McMillan Subject: Re: good pc but bad performance,why? Date: Wed, 7 Apr 2004 17:21:43 +0530 User-Agent: KMail/1.6.1 Cc: huang yaqin , pgsql-performance@postgresql.org References: <0HVS00G7FMQO35@mail.gthome.com> <1081337381.522.57.camel@lamb.mcmillan.net.nz> In-Reply-To: <1081337381.522.57.camel@lamb.mcmillan.net.nz> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200404071721.43059.shridhar_daithankar@persistent.co.in> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/124 X-Sequence-Number: 6424 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