Re: Changing the default wal_sync_method to open_sync for Win32? - Mailing list pgsql-hackers

From Kenneth Marshall
Subject Re: Changing the default wal_sync_method to open_sync for Win32?
Date
Msg-id 20050317141258.GA13019@it.is.rice.edu
Whole thread Raw
In response to Changing the default wal_sync_method to open_sync for Win32?  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
On Wed, Mar 16, 2005 at 11:20:12PM -0500, Bruce Momjian wrote:
> 
> Basically we do open_datasync -> fdatasync -> fsync.  This is
> empirically what we found to be fastest on most operating systems, and
> we default to the first one that exists on the operating system.
> 
> Notice we never default to open_sync.  However, on Win32, Magnus got a
> 60% speedup by using open_sync, implemented using
> FILE_FLAG_WRITE_THROUGH.  Now, because this the fastest on Win32, I
> think we should default to open_sync on Win32.  The attached patch
> implements this.
> 
> 2.  Another question is what to do with 8.0.X?  Do we backpatch this for
> Win32 performance?  Can we test it enough to know it will work well? 
> 8.0.2 is going to have a more rigorous testing cycle because of the
> buffer manager changes.
> 
My preference would be to back-patch to 8.0.1. I have some projects
where the performance difference will decide whether or not they go
with MSSQL or PostgreSQL.

Ken


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Avoiding unnecessary writes during relation drop and truncate
Next
From: Christopher Browne
Date:
Subject: Re: Real-Time Vacuum Possibility