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

From Tom Lane
Subject Re: [pgsql-hackers-win32] win32 performance - fsync question
Date
Msg-id 26678.1111088179@sss.pgh.pa.us
Whole thread Raw
Responses Re: [pgsql-hackers-win32] win32 performance - fsync question
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Tom Lane wrote:
>> 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?

> Ah, I remember now.  On Win32 our fsync is:
>     #define fsync(a)    _commit(a)
> I am wondering if we should call the new mode open_commit or
> open_writethrough.  Our typical rule is to tie it to the API call, which
> should suggest open_commit.

fsync_writethrough, perhaps.  I don't see any "open" about it.

            regards, tom lane

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Windows, gettext/libintl, pg_sprintf and friends
Next
From: Bruce Momjian
Date:
Subject: Re: [pgsql-hackers-win32] win32 performance - fsync question