summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian2008-12-06 21:34:27 +0000
committerBruce Momjian2008-12-06 21:34:27 +0000
commit64b3d98baaf96afea815b0c37ff918f02fda11c9 (patch)
tree7c23ef65c0064bad0f12259504ce0cc0b19f7e2b
parent92687ef164d0e3a0113b56e736c38a9389d3a1a6 (diff)
Document that non-data journaling is a recommended mount option.
-rw-r--r--doc/src/sgml/wal.sgml15
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
index 907e9c8762..7ae6c053d7 100644
--- a/doc/src/sgml/wal.sgml
+++ b/doc/src/sgml/wal.sgml
@@ -135,6 +135,21 @@
roll-forward recovery, also known as REDO.)
</para>
+ <tip>
+ <para>
+ Because <acronym>WAL</acronym> restores database file
+ contents after a crash, it is not necessary to use a
+ journaled filesystem; in fact, journaling overhead can
+ reduce performance. For best performance, turn off
+ <emphasis>data</emphasis> journaling as a filesystem mount
+ option, e.g. use <literal>data=writeback</> on Linux.
+ Meta-data journaling (e.g. file creation and directory
+ modification) is still desirable for faster rebooting after
+ a crash.
+ </para>
+ </tip>
+
+
<para>
Using <acronym>WAL</acronym> results in a
significantly reduced number of disk writes, because only the log