X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 0DF419FB2A0 for ; Thu, 3 Aug 2006 04:17:23 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 60760-05 for ; Thu, 3 Aug 2006 04:17:17 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mx00.ext.bfk.de (mx00.ext.bfk.de [217.29.46.125]) by postgresql.org (Postfix) with ESMTP id BC7F99FB282 for ; Thu, 3 Aug 2006 04:17:18 -0300 (ADT) Received: from fweimer by bfk.de with local id 1G8XSC-0007Ik-Pe; Thu, 03 Aug 2006 09:17:12 +0200 To: "Koth, Christian (DWBI)" Cc: "Milen Kulev" , Subject: Re: XFS filessystem for Datawarehousing References: From: Florian Weimer Date: Thu, 03 Aug 2006 09:17:12 +0200 In-Reply-To: (Christian Koth's message of "Thu, 3 Aug 2006 01:10:39 -0600") Message-ID: <8264haffuv.fsf@mid.bfk.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.014 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200608/39 X-Sequence-Number: 20224 * Christian Koth: > For what reason are you planning to use a journaling FS? I think > using WAL, fsyncing every transaction and using a journaling FS is > tautologous. The journal is absolutely required to preserve the integrity of the file system's own on-disk data structures after a crash. Even if you've got a trustworthy file system checker (there are surprisingly few of them, especially for advanced file systems without fixed data structure locations), running it after a crash usually leads to unacceptably high downtime. -- Florian Weimer BFK edv-consulting GmbH http://www.bfk.de/ Durlacher Allee 47 tel: +49-721-96201-1 D-76131 Karlsruhe fax: +49-721-96201-99