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 3aa22bcf9e7f2676efda16c43380b0e36a782c36..15af6693f5d7283fa84be618f341c52910842bc7 100644 (file)
--- 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