aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/transam/xlog.c
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2011-03-10 20:02:52 -0500
committerBruce Momjian <bruce@momjian.us>2011-03-10 20:02:52 -0500
commit5ca543fb2e2ca5becdb6505ac22aaf7218e842cf (patch)
tree0fe696091a8f8bf98fba784d019e8e4f72c6e91b /src/backend/access/transam/xlog.c
parent26174d5fd0dec01bbbc4e766ed32b9a50a019c29 (diff)
downloadpostgresql-5ca543fb2e2ca5becdb6505ac22aaf7218e842cf.tar.gz
postgresql-5ca543fb2e2ca5becdb6505ac22aaf7218e842cf.zip
Clarify C comment that O_SYNC/O_FSYNC are really the same settting, as
opposed to O_DSYNC.
Diffstat (limited to 'src/backend/access/transam/xlog.c')
-rw-r--r--src/backend/access/transam/xlog.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/access/transam/xlog.c b/src/backend/access/transam/xlog.c
index 3aa22bcf9e7..15af6693f5d 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