|
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 $ --> |
2 | 2 |
|
3 | 3 | <chapter id="wal"> |
4 | 4 | <title>Reliability and the Write-Ahead Log</title> |
|
138 | 138 | <tip> |
139 | 139 | <para> |
140 | 140 | Because <acronym>WAL</acronym> restores database file |
141 | | - contents after a crash,it is not necessaryto use a |
142 | | -journaled filesystem for reliability. In fact, journaling |
| 141 | + contents after a crash,journaled filesystems are necessaryfor |
| 142 | +reliable storage of the data files or WAL files. In fact, journaling |
143 | 143 | overhead can reduce performance, especially if journaling |
144 | 144 | causes file system <emphasis>data</emphasis> to be flushed |
145 | 145 | to disk. Fortunately, data flushing during journaling can |
|