From c9b142d96577c0a37a62215b99c98d52c8fbc4e1 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Thu, 8 Jul 2010 16:44:12 +0000 Subject: [PATCH] Doc change: effected -> affected, per correction from Matthew Wakeling --- 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 f1c95b3484..0c83032968 100644 --- a/doc/src/sgml/wal.sgml +++ b/doc/src/sgml/wal.sgml @@ -1,4 +1,4 @@ - + Reliability and the Write-Ahead Log @@ -98,7 +98,7 @@ command forces all data from the BBU to the disks, eliminating much of the benefit of the BBU. You can run the utility src/tools/fsync in the PostgreSQL source tree to see - if you are effected. If you are effected, the performance benefits + if you are affected. If you are affected, the performance benefits of the BBU cache can be regained by turning off write barriers in the file system or reconfiguring the disk controller, if that is an option. If write barriers are turned off, make sure the battery -- 2.40.0