Skip site navigation (1) Skip section navigation (2)

Re: [pgsql-hackers-win32] win32 performance - fsync question

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Magnus Hagander <mha(at)sollentuna(dot)net>,Michael Paesold <mpaesold(at)gmx(dot)at>, pgsql-hackers(at)postgresql(dot)org,pgsql-hackers-win32(at)postgresql(dot)org,Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com>
Subject: Re: [pgsql-hackers-win32] win32 performance - fsync question
Date: 2005-03-17 18:41:00
Message-ID: 26109.1111084860@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-hackers-win32pgsql-patches
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> However, I do prefer this patch and let Win32 have the same write cache
> issues as Unix, for consistency.

I agree that the open flag is more nearly O_DSYNC than O_SYNC.

ISTM Windows' idea of fsync is quite different from Unix's and therefore
we should name the wal_sync_method that invokes it something different
than fsync.  "write_through" or some such?  We already have precedent
that not all wal_sync_method values are available on all platforms.

I'm not taking a position on which the default should be ...

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2005-03-17 18:42:56
Subject: Re: Changing the default wal_sync_method to open_sync for
Previous:From: Merlin MoncureDate: 2005-03-17 18:36:29
Subject: Re: securing pg_proc

pgsql-patches by date

Next:From: Bruce MomjianDate: 2005-03-17 18:53:11
Subject: Re: [pgsql-hackers-win32] win32 performance - fsync question
Previous:From: Bruce MomjianDate: 2005-03-17 18:35:14
Subject: Re: [pgsql-hackers-win32] win32 performance - fsync question

pgsql-hackers-win32 by date

Next:From: Bruce MomjianDate: 2005-03-17 18:42:56
Subject: Re: Changing the default wal_sync_method to open_sync for
Previous:From: Bruce MomjianDate: 2005-03-17 18:35:14
Subject: Re: [pgsql-hackers-win32] win32 performance - fsync question

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group