aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2008-12-18 22:21:16 +0000
committerBruce Momjian <bruce@momjian.us>2008-12-18 22:21:16 +0000
commitfa6116a3da725a5a1693917dccff1f2f0d892600 (patch)
treecfd4e887782e358c32ea7a9831b9ca236074bfa5
parent4ac592be6c7ca089f302eb8787df44080ee2f8ee (diff)
downloadpostgresql-fa6116a3da725a5a1693917dccff1f2f0d892600.tar.gz
postgresql-fa6116a3da725a5a1693917dccff1f2f0d892600.zip
Clarify documentation that journaling is not required for WAL or data files.
-rw-r--r--doc/src/sgml/wal.sgml6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
index e69463a9e22..a54fbc685e0 100644
--- a/doc/src/sgml/wal.sgml
+++ b/doc/src/sgml/wal.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.55 2008/12/10 11:05:49 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.56 2008/12/18 22:21:16 momjian Exp $ -->
<chapter id="wal">
<title>Reliability and the Write-Ahead Log</title>
@@ -138,8 +138,8 @@
<tip>
<para>
Because <acronym>WAL</acronym> restores database file
- contents after a crash, it is not necessary to use a
- journaled filesystem for reliability. In fact, journaling
+ contents after a crash, journaled filesystems are necessary for
+ reliable storage of the data files or WAL files. 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