From: Bruce Momjian Date: Fri, 11 Mar 2011 01:02:52 +0000 (-0500) Subject: Clarify C comment that O_SYNC/O_FSYNC are really the same settting, as X-Git-Tag: REL9_1_ALPHA5~118 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=5ca543fb2e2ca5becdb6505ac22aaf7218e842cf;p=postgresql Clarify C comment that O_SYNC/O_FSYNC are really the same settting, as opposed to O_DSYNC. --- diff --git a/src/backend/access/transam/xlog.c b/src/backend/access/transam/xlog.c index 3aa22bcf9e..15af6693f5 100644 --- a/src/backend/access/transam/xlog.c +++ b/src/backend/access/transam/xlog.c @@ -8600,7 +8600,7 @@ get_sync_bit(int method) /* * Optimize writes by bypassing kernel cache with O_DIRECT when using - * O_SYNC, O_DSYNC or O_FSYNC. But only if archiving and streaming are + * O_SYNC/O_FSYNC and O_DSYNC. But only if archiving and streaming are * disabled, otherwise the archive command or walsender process will read * the WAL soon after writing it, which is guaranteed to cause a physical * read if we bypassed the kernel cache. We also skip the