From 382af3a95406c1ee9a4a5647eb7586d1432196e3 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 18 Dec 2008 22:34:21 +0000
Subject: [PATCH] Add "not" to wal journaling text.
---
doc/src/sgml/wal.sgml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
index a54fbc685e0..e5750b62dc5 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.56 2008/12/18 22:21:16 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.57 2008/12/18 22:34:21 momjian Exp $ -->
<chapter id="wal">
<title>Reliability and the Write-Ahead Log</title>
@@ -138,7 +138,7 @@
<tip>
<para>
Because <acronym>WAL</acronym> restores database file
- contents after a crash, journaled filesystems are necessary for
+ contents after a crash, journaled filesystems are not 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
--
GitLab