X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.192]) by svr1.postgresql.org (Postfix) with ESMTP id 3CB61CCDB7 for ; Fri, 18 Jul 2003 19:07:27 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr4.postgresql.org [64.117.224.192]) (amavisd-new, port 10024) with ESMTP id 15590-03 for ; Fri, 18 Jul 2003 19:07:57 +0000 (GMT) Received: from davinci.ethosmedia.com (unknown [209.10.40.251]) by svr1.postgresql.org (Postfix) with ESMTP id F0F1ACCDB0 for ; Fri, 18 Jul 2003 16:07:24 -0300 (ADT) Received: from [66.219.92.2] (HELO temoku) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3229373; Fri, 18 Jul 2003 12:08:13 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: , Subject: Re: Sanity check requested Date: Fri, 18 Jul 2003 12:07:00 -0700 User-Agent: KMail/1.4.3 Cc: , "Vincent van Leeuwen" References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200307181207.00746.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/304 X-Sequence-Number: 2597 Nick, > ...About one year ago I considered moving to a journaling file system, but > opted not to because it seems like that's what WAL does for us already. H= ow > does putting a journaling file system under it add more reliability? It lets you restart your server quickly after an unexpected power-out. Ext= 2=20 is notoriously bad about this. Also, WAL cannot necessarily recover properly if the underlying filesystem = is=20 corrupted. > I also guessed that a journaling file system would add overhead because n= ow > a write to the WAL file could itself be deferred and logged elsewhere. You are correct. --=20 -Josh Berkus Aglio Database Solutions San Francisco