Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 5BBED63228C for ; Tue, 10 Nov 2009 13:07:32 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 90184-04 for ; Tue, 10 Nov 2009 17:07:22 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mail.postgresql.org (Postfix) with ESMTP id 1A20062E33C for ; Tue, 10 Nov 2009 13:07:20 -0400 (AST) Received: by fxm27 with SMTP id 27so245613fxm.3 for ; Tue, 10 Nov 2009 09:07:19 -0800 (PST) Received: by 10.103.81.2 with SMTP id i2mr125323mul.81.1257872839294; Tue, 10 Nov 2009 09:07:19 -0800 (PST) Received: from ?192.168.0.76? (rrcs-64-183-7-130.west.biz.rr.com [64.183.7.130]) by mx.google.com with ESMTPS id n10sm3712916mue.17.2009.11.10.09.07.16 (version=SSLv3 cipher=RC4-MD5); Tue, 10 Nov 2009 09:07:18 -0800 (PST) Message-ID: <4AF99DC2.9040607@emolecules.com> Date: Tue, 10 Nov 2009 09:07:14 -0800 From: Craig James User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: limiting performance impact of wal archiving. References: <8a1bfe660911100355l34a557ffj8244079c1fb689b5@mail.gmail.com> <8a1bfe660911100700l2a44f638m97ea6136b65deb21@mail.gmail.com> <8a1bfe660911100729q42ac732cga9bbadd52e2533dd@mail.gmail.com> <4AF99666.5090705@2ndquadrant.com> <8a1bfe660911100852l5573ab30ne91c6d8937dc836b@mail.gmail.com> In-Reply-To: <8a1bfe660911100852l5573ab30ne91c6d8937dc836b@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 200911/109 X-Sequence-Number: 36277 On Tue, Nov 10, 2009 at 5:35 PM, Greg Smith wrote: > Given the current quality of Linux code, I hesitate to use anything but ext3 > because I consider that just barely reliable enough even as the most popular > filesystem by far. JFS and XFS have some benefits to them, but none so > compelling to make up for how much less testing they get. That said, there > seem to be a fair number of people happily running high-performance > PostgreSQL instances on XFS. I thought the common wisdom was to use ext2 for the WAL, since the WAL is a journal system, and ext3 would essentially be journaling the journal. Is that not true? Craig