postgres.git / summary / log / commit / refs

commit    c9b142d96577c0a37a62215b99c98d52c8fbc4e1
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Thu Jul 08 16:44:12 2010 +0000
First released in: 9.0.0

    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 f1c95b34848..0c83032968a 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.67 2010/07/07 14:42:09 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.68 2010/07/08 16:44:12 momjian Exp $ -->
 
 <chapter id="wal">
  <title>Reliability and the Write-Ahead Log</title>
@@ -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
    <filename>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


[parent: 7f882768dc8f]