Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 6E09C475F1A for ; Fri, 24 Jan 2003 21:22:09 -0500 (EST) Received: from davinci.ethosmedia.com (unknown [209.10.40.251]) by postgresql.org (Postfix) with ESMTP id 0CD604758E6 for ; Fri, 24 Jan 2003 21:21:53 -0500 (EST) Received: from [66.219.92.2] (HELO chocolate-mousse) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 2325202; Fri, 24 Jan 2003 18:22:00 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Kevin Brown , pgsql-performance@postgresql.org Subject: Re: Mount options for Ext3? Date: Fri, 24 Jan 2003 18:22:33 -0800 X-Mailer: KMail [version 1.4] References: <200301241120.14404.josh@agliodbs.com> <20030125003011.GA28252@filer> In-Reply-To: <20030125003011.GA28252@filer> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200301241822.33731.josh@agliodbs.com> X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/319 X-Sequence-Number: 966 Kevin, > So if I'm right about that, then you might consider using the > "data=3Dwriteback" option for the filesystem that contains the actual > data (usually /usr/local/pgsql/data), but I'd use the default > ("data=3Dordered") at the very least (I suppose there's no harm in using > "data=3Djournal" if you're willing to put up with the performance hit, > but it's not clear to me what benefit, if any, there is) for > everything else. Well, the only reason I use Ext3 rather than Ext2 is to prevent fsck's on= =20 restart after a crash. So I'm interested in the data option that gives t= he=20 minimum performance hit, even if it means that I sacrifice some reliability= .=20=20=20 I'm running with fsynch on, and the DB is on a mirrored drive array, so I'm= =20 not too worried about filesystem-level errors. So would that be "data=3Dwriteback"? --=20 -Josh Berkus Aglio Database Solutions San Francisco