diff options
| author | Bruce Momjian | 2008-12-10 11:05:49 +0000 |
|---|---|---|
| committer | Bruce Momjian | 2008-12-10 11:05:49 +0000 |
| commit | 19219ca0c65ab76a97c923422d62c18c7a86d46f (patch) | |
| tree | 3944b552ec8914de66f9e45cfadd5f94acada180 | |
| parent | f767f737e4e1697f5f6840ae33b57de94ce955a8 (diff) | |
Update journaling performance docs based on comments by Michael Renner.
| -rw-r--r-- | doc/src/sgml/wal.sgml | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml index 7ae6c053d7..15cd5baec3 100644 --- a/doc/src/sgml/wal.sgml +++ b/doc/src/sgml/wal.sgml @@ -139,13 +139,13 @@ <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. + journaled filesystem for reliability. In fact, journaling + overhead can reduce performance, especially if journaling + causes file system <emphasis>data</emphasis> to be flushed + to disk. Fortunately, data flushing during journaling can + often be disabled with a filesystem mount option, e.g. + <literal>data=writeback</> on a Linux ext3 file system. + Journaled file systems do improve boot speed after a crash. </para> </tip> |