Re: limiting performance impact of wal archiving.

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Craig James <craig_james(at)emolecules(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: limiting performance impact of wal archiving.
Date: 2009-11-10 17:10:45
Message-ID: dcc563d10911100910y9229f50pdc150f3ea41ae9e8@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, Nov 10, 2009 at 10:07 AM, Craig James
<craig_james(at)emolecules(dot)com> wrote:
> On Tue, Nov 10, 2009 at 5:35 PM, Greg Smith <greg(at)2ndquadrant(dot)com> 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?

Yep, ext2 for pg_xlog is fine.

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Greg Smith 2009-11-10 17:26:03 Re: limiting performance impact of wal archiving.
Previous Message Craig James 2009-11-10 17:07:14 Re: limiting performance impact of wal archiving.