Re: Allowing WAL fsync to be done via O_SYNC - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Allowing WAL fsync to be done via O_SYNC
Date
Msg-id 14658.984683064@sss.pgh.pa.us
Whole thread Raw
In response to RE: Allowing WAL fsync to be done via O_SYNC  ("Mikheev, Vadim" <vmikheev@SECTORBASE.COM>)
Responses Re: Allowing WAL fsync to be done via O_SYNC  (Alfred Perlstein <bright@wintelcom.net>)
Re: Allowing WAL fsync to be done via O_SYNC  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
"Mikheev, Vadim" <vmikheev@SECTORBASE.COM> writes:
> ... I would either
> use fsync as default or don't deal with O_SYNC at all.
> But if O_DSYNC is defined and O_DSYNC != O_SYNC then we should
> use O_DSYNC by default.

Hm.  We could do that reasonably painlessly as a compile-time test in
xlog.c, but I'm not clear on how it would play out as a GUC option.
Peter, what do you think about configuration-dependent defaults for
GUC variables?
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Mikheev, Vadim"
Date:
Subject: RE: Allowing WAL fsync to be done via O_SYNC
Next
From: Alfred Perlstein
Date:
Subject: Re: Allowing WAL fsync to be done via O_SYNC