10000 Clarify C comment that O_SYNC/O_FSYNC are really the same settting, as · postgres/postgres@5ca543f · GitHub
[go: up one dir, main page]
Skip to content

Commit 5ca543f

Browse files
bmomjianbmomjian
committed
Clarify C comment that O_SYNC/O_FSYNC are really the same settting, as
opposed to O_DSYNC.
1 parent 26174d5 commit 5ca543f

File tree

1 file changed

+1
-1
lines changed
  • src/backend/access/transam

1 file changed

+1
-1
lines changed

‎src/backend/access/transam/xlog.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8600,7 +8600,7 @@ get_sync_bit(int method)
86008600

86018601
/*
86028602
* Optimize writes by bypassing kernel cache with O_DIRECT when using
8603-
* O_SYNC, O_DSYNC or O_FSYNC. But only if archiving and streaming are
8603+
* O_SYNC/O_FSYNC and O_DSYNC. But only if archiving and streaming are
86048604
* disabled, otherwise the archive command or walsender process will read
86058605
* the WAL soon after writing it, which is guaranteed to cause a physical
86068606
* read if we bypassed the kernel cache. We also skip the

0 commit comments

Comments
 (0)
0