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 01:17:43
Message-ID: 11392.1289956663@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

I wrote:
> The fsync is associated with the write, which is not done with insert
> lock held. We're not quite that dumb.

But wait --- are you thinking of the call path where a write (and
possible fsync) is forced during AdvanceXLInsertBuffer because there's
no WAL buffer space left? If so, that's *exactly* the scenario that
can be expected to be less common with more buffer space.

regards, tom lane

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2010-11-17 01:22:08 Re: Defaulting wal_sync_method to fdatasync on Linux for 9.1?
Previous Message Josh Berkus 2010-11-17 01:17:42 Re: Defaulting wal_sync_method to fdatasync on Linux for 9.1?