Skip to content

P
Postgres FD Implementation
Commit fa6116a3 authored by Bruce Momjian's avatar Bruce Momjian
Browse files
Options

Clarify documentation that journaling is not required for WAL or data files.

parent 4ac592be
Hide whitespace changes
Inline Side-by-side
Showing with 3 additions and 3 deletions
doc/src/sgml/wal.sgml
View file @ fa6116a3
<!-- $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"> <chapter id="wal">
<title>Reliability and the Write-Ahead Log</title> <title>Reliability and the Write-Ahead Log</title>
...@@ -138,8 +138,8 @@ ...@@ -138,8 +138,8 @@
<tip> <tip>
<para> <para>
Because <acronym>WAL</acronym> restores database file Because <acronym>WAL</acronym> restores database file
contents after a crash, it is not necessary to use a contents after a crash, journaled filesystems are necessary for
journaled filesystem for reliability. In fact, journaling reliable storage of the data files or WAL files. In fact, journaling
overhead can reduce performance, especially if journaling overhead can reduce performance, especially if journaling
causes file system <emphasis>data</emphasis> to be flushed causes file system <emphasis>data</emphasis> to be flushed
to disk. Fortunately, data flushing during journaling can to disk. Fortunately, data flushing during journaling can
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment