X-Original-To: pgsql-performance@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 23C6D476083 for ; Wed, 2 Apr 2003 12:01:00 -0500 (EST) Received: from localhost.localdomain (208-41-234-242.client.dsl.net [208.41.234.242]) by postgresql.org (Postfix) with ESMTP id C1EF1475ED4 for ; Wed, 2 Apr 2003 12:00:58 -0500 (EST) Received: from endeavour (endeavour.pointhere.net [192.168.2.11]) by localhost.localdomain (8.11.6/8.11.6) with SMTP id h32GoE905563; Wed, 2 Apr 2003 11:50:15 -0500 Message-ID: <0a6f01c2f93a$6907bf50$0b02a8c0@pointhere.net> Reply-To: "Jeffrey D. Brower" From: "Jeffrey D. Brower" To: "Andreas Kostyrka" Cc: "Bruce Momjian" , , "Shankar K" , "eric soroos" References: <26287373.1162931668@[4.42.179.151]> <1049296398.20242.325.camel@andi-lap> <0a3001c2f92d$c975a490$0b02a8c0@pointhere.net> <1049298455.21669.333.camel@andi-lap> Subject: Re: ext3 filesystem / linux 7.3 Date: Wed, 2 Apr 2003 12:07:57 -0500 Organization: A Basic Marketing Company MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Status: No, hits=-11.2 required=5.0 tests=BAYES_20,QUOTED_EMAIL_TEXT,RCVD_IN_NJABL,REFERENCES, X_NJABL_OPEN_PROXY 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/22 X-Sequence-Number: 1528 >> This would indicate that the PG transactioning is complimentary to the filesystem journaling, not duplication. >It's both. See the -o data=journal|data=ordered|data=writeback mount >time option. I did a RTFM on that but I am now confused again. I am wondering what the *best* setting is with ext3. When I RTFM the man page for mount, the data=writeback option says plainly that it is fastest but in a crash old data is quite possibly on the dataset. The safest *looks* to be data=journal since the journaling happens before writes are committed to the file (and presumably the journal is used to update the file on the disk to apply the journal entry to the disk file?) and the default is data=ordered which says write to the disk AND THEN to the journal (which seems bizarre to me). 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. Jeff