Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 6AADA6326D1 for ; Tue, 10 Nov 2009 13:10:54 -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 90474-10 for ; Tue, 10 Nov 2009 17:10:46 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.223.182]) by mail.postgresql.org (Postfix) with ESMTP id 1E6C163228C for ; Tue, 10 Nov 2009 13:10:45 -0400 (AST) Received: by iwn12 with SMTP id 12so184853iwn.15 for ; Tue, 10 Nov 2009 09:10:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=amkJUbcThuUflQ0TBox5zkCrP2x9trQiJMAqkCe9Zks=; b=YpmIz5y7pCwSc2btfuPt67oOXvHsiwdlEWFvGsEkxijayYDXAHSL6SBzUBx7dXaVYA 8Z4mvYuwtCYiPmxfdHZegzfGnnQ9g8+dyWZ9oGchDOoBI4UdNv4WCafVmyUd8Qn/mZIE ThMnZLC9OhZNYIzpO3E6KM7o5TOA3tJC7QxCk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=SkicN1zcRTWRYP/eASTNFlIJn6TiZkjscfuvC6ZQVdvBAvVaBO0sj6TUiuWbnlqk2m 5NU10zJ0h2Vs6Il8QLBO5mXuaH7psbkk/plzsQAsbzEgVabGZ10idC2UtvIhDz3wpVA0 kjFPC9o1zJZVw+ZyKGzvbRCmPU3vknrJjJIn4= MIME-Version: 1.0 Received: by 10.231.28.143 with SMTP id m15mr545440ibc.23.1257873045098; Tue, 10 Nov 2009 09:10:45 -0800 (PST) In-Reply-To: <4AF99DC2.9040607@emolecules.com> References: <8a1bfe660911100355l34a557ffj8244079c1fb689b5@mail.gmail.com> <8a1bfe660911100700l2a44f638m97ea6136b65deb21@mail.gmail.com> <8a1bfe660911100729q42ac732cga9bbadd52e2533dd@mail.gmail.com> <4AF99666.5090705@2ndquadrant.com> <8a1bfe660911100852l5573ab30ne91c6d8937dc836b@mail.gmail.com> <4AF99DC2.9040607@emolecules.com> Date: Tue, 10 Nov 2009 10:10:45 -0700 Message-ID: Subject: Re: limiting performance impact of wal archiving. From: Scott Marlowe To: Craig James Cc: pgsql-performance@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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/110 X-Sequence-Number: 36278 On Tue, Nov 10, 2009 at 10:07 AM, Craig James wrote: > 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. =A0JFS and XFS have some benefits to them, but none s= o >> compelling to make up for how much less testing they get. =A0That 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. =A0= Is > that not true? Yep, ext2 for pg_xlog is fine.