Re: Defaulting wal_sync_method to fdatasync on Linux for 9.1?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Greg Smith <greg(at)2ndquadrant(dot)com>
Cc: Marti Raudsepp <marti(at)juffo(dot)org>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Defaulting wal_sync_method to fdatasync on Linux for 9.1?
Date: 2010-11-16 23:10:12
Message-ID: AANLkTin=nohuBvy94eqekd6gajyVXfEPh3JK8xKrsC0v@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, Nov 16, 2010 at 3:39 PM, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
> I want to next go through and replicate some of the actual database level
> tests before giving a full opinion on whether this data proves it's worth
> changing the wal_sync_method detection.  So far I'm torn between whether
> that's the right approach, or if we should just increase the default value
> for wal_buffers to something more reasonable.

How about both?

open_datasync seems problematic for a number of reasons - you get an
immediate write-through whether you need it or not, including, as you
point out, the case where the you want to write several blocks at once
and then force them all out together.

And 64kB for a ring buffer just seems awfully small.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Josh Berkus 2010-11-16 23:25:13 Re: Defaulting wal_sync_method to fdatasync on Linux for 9.1?
Previous Message Greg Smith 2010-11-16 20:39:20 Re: Defaulting wal_sync_method to fdatasync on Linux for 9.1?