X-Original-To: pgsql-performance@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 4F5CF4762D7 for ; Wed, 2 Apr 2003 15:05:44 -0500 (EST) Received: from davinci.ethosmedia.com (unknown [209.10.40.251]) by postgresql.org (Postfix) with ESMTP id 8A3F94762F6 for ; Wed, 2 Apr 2003 15:05:39 -0500 (EST) Received: from [66.219.92.2] (HELO temoku) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 2938646; Wed, 02 Apr 2003 12:05:26 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: "Jeffrey D. Brower" , "Andreas Kostyrka" Subject: Re: ext3 filesystem / linux 7.3 Date: Wed, 2 Apr 2003 12:05:30 -0800 User-Agent: KMail/1.4.3 Cc: "Bruce Momjian" , , "Shankar K" , "eric soroos" References: <26287373.1162931668@[4.42.179.151]> <1049298455.21669.333.camel@andi-lap> <0a6f01c2f93a$6907bf50$0b02a8c0@pointhere.net> In-Reply-To: <0a6f01c2f93a$6907bf50$0b02a8c0@pointhere.net> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200304021205.30075.josh@agliodbs.com> X-Spam-Status: No, hits=-31.6 required=5.0 tests=BAYES_10,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_KMAIL autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) X-Archive-Number: 200304/23 X-Sequence-Number: 1529 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= =20 prevent a painful fsck process on an unexpected power-out. You are not, as= a=20 rule, terribly concerned with journaling the data as PostgreSQL already=20 provides some data recovery protection through WAL. As a result, on my one server where I have to use Ext3 (I use Reiser on mos= t=20 machines, and have never had a problem except for one disaster when upgradi= ng=20 Reiser versions), the $PGDATA is mounted "noatime,data=3Dwriteback" (BTW, I found that combining "data=3Dwriteback" with Linux LVM on RedHat 8.= 0=20 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= =20 unlimited, then maybe you want to enable data=3Djournal just for the protec= tion=20 against corruption of the WAL and clog files.=20=20=20 --=20 -Josh Berkus Aglio Database Solutions San Francisco