> One point that I no longer recall the reasoning behind is that xlog.c
> doesn't think O_SYNC is a preferable default over fsync. We'd
certainly
> want to hack xlog.c to change its mind about that, at least on
Windows;
> assuming that the FILE_FLAG way is indeed faster.
I also confirmed that the totally un-cached mode in windows
(FILE_FLAG_WRITE_THROUGH | FILE_FLAG_NO_BUFFERING) will only work if the
amount of data written is some multiple of 512 bytes. Can WAL work
under this restriction?
Merlin