From 487b757b7a0b560cbb612164a66888cd5421e124 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Tue, 9 Aug 2005 04:50:44 +0000 Subject: Clarify wal_sync_method options in documentation. --- doc/src/sgml/runtime.sgml | 39 ++++++++++++++++++++++++++++++++------- 1 file changed, 32 insertions(+), 7 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index 91071ddc4ec..299fc28a7db 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1,5 +1,5 @@ @@ -1724,13 +1724,38 @@ SET ENABLE_SEQSCAN TO OFF; Method used for forcing WAL updates out to disk. Possible - values are - fsync (call fsync() at each commit), - fdatasync (call fdatasync() at each commit), - fsync_writethrough (force write-through of any disk write cache), - open_sync (write WAL files with open() option O_SYNC), and - open_datasync (write WAL files with open() option O_DSYNC). + values are: + + + + + open_datasync (write WAL files with open() option O_DSYNC) + + + + + fdatasync (call fdatasync() at each commit), + + + + + fsync (call fsync() at each commit) + + + + + open_sync (write WAL files with open() option O_SYNC) + + + + + fsync_writethrough (force write-through of any disk write cache) + + + + Not all of these choices are available on all platforms. + The top-most supported option is used as the default. If fsync is off then this setting is irrelevant. This option can only be set at server start or in the postgresql.conf file. -- cgit v1.2.3