Re: limiting performance impact of wal archiving.

On Tue, 10 Nov 2009, Greg Smith wrote:

> Laurent Laborde wrote:
>> It is on a separate array which does everything but tablespace (on a
>> separate array) and indexspace (another separate array).
>> 
> On Linux, the types of writes done to the WAL volume (where writes are 
> constantly being flushed) require the WAL volume not be shared with anything 
> else for that to perform well.  Typically you'll end up with other things 
> being written out too because it can't just selectively flush just the WAL 
> data.  The whole "write barriers" implementation should fix that, but in 
> practice rarely does.

I believe that this is more a EXT3 problem than a linux problem.

David Lang