From 5ca543fb2e2ca5becdb6505ac22aaf7218e842cf Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Thu, 10 Mar 2011 20:02:52 -0500 Subject: [PATCH] Clarify C comment that O_SYNC/O_FSYNC are really the same settting, as opposed to O_DSYNC. --- src/backend/access/transam/xlog.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 -- 2.40.0