Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit fa6116a

Browse files
committed
Clarify documentation that journaling is not required for WAL or data files.
1 parent 4ac592b commit fa6116a

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

doc/src/sgml/wal.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.55 2008/12/10 11:05:49 momjian Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.56 2008/12/18 22:21:16 momjian Exp $ -->
22

33
<chapter id="wal">
44
<title>Reliability and the Write-Ahead Log</title>
@@ -138,8 +138,8 @@
138138
<tip>
139139
<para>
140140
Because <acronym>WAL</acronym> restores database file
141-
contents after a crash, it is not necessary to use a
142-
journaled filesystem for reliability. In fact, journaling
141+
contents after a crash, journaled filesystems are necessary for
142+
reliable storage of the data files or WAL files. In fact, journaling
143143
overhead can reduce performance, especially if journaling
144144
causes file system <emphasis>data</emphasis> to be flushed
145145
to disk. Fortunately, data flushing during journaling can

0 commit comments

Comments
 (0)