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

From Alfred Perlstein
Subject Re: Allowing WAL fsync to be done via O_SYNC
Date
Msg-id 20010315111724.Z29888@fw.wintelcom.net
Whole thread Raw
In response to Re: Allowing WAL fsync to be done via O_SYNC  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Allowing WAL fsync to be done via O_SYNC
List pgsql-hackers
* Tom Lane <tgl@sss.pgh.pa.us> [010315 11:07] wrote:
> "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?

Sorry, what's a GUC? :)

-- 
-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org]



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Allowing WAL fsync to be done via O_SYNC
Next
From: Peter Eisentraut
Date:
Subject: Re: Allowing WAL fsync to be done via O_SYNC