Re: Defaulting wal_sync_method to fdatasync on Linux for 9.1?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-performance(at)postgresql(dot)org, Josh Berkus <josh(at)agliodbs(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>
Subject: Re: Defaulting wal_sync_method to fdatasync on Linux for 9.1?
Date: 2010-11-17 00:51:28
Message-ID: 10822.1289955088@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Andres Freund <andres(at)anarazel(dot)de> writes:
> On Wednesday 17 November 2010 00:31:34 Tom Lane wrote:
>> Well, we're not going to increase the default to gigabytes

> Especially not as I don't think it will have any effect after wal_segment_size
> as that will force a write-out anyway. Or am I misremembering the
> implementation?

Well, there's a forced fsync after writing the last page of an xlog
file, but I don't believe that proves that more than 16MB of xlog
buffers is useless. Other processes could still be busy filling the
buffers.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Andres Freund 2010-11-17 01:01:24 Re: Defaulting wal_sync_method to fdatasync on Linux for 9.1?
Previous Message Andres Freund 2010-11-17 00:30:09 Re: Defaulting wal_sync_method to fdatasync on Linux for 9.1?