Skip to content

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

Doc change: effected -> affected, per correction from Matthew Wakeling

parent 7f882768
Hide whitespace changes
Inline Side-by-side
Showing with 2 additions and 2 deletions
doc/src/sgml/wal.sgml
View file @ c9b142d9
<!-- $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"> <chapter id="wal">
<title>Reliability and the Write-Ahead Log</title> <title>Reliability and the Write-Ahead Log</title>
...@@ -98,7 +98,7 @@ ...@@ -98,7 +98,7 @@
command forces all data from the BBU to the disks, eliminating much command forces all data from the BBU to the disks, eliminating much
of the benefit of the BBU. You can run the utility of the benefit of the BBU. You can run the utility
<filename>src/tools/fsync</> in the PostgreSQL source tree to see <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 of the BBU cache can be regained by turning off write barriers in
the file system or reconfiguring the disk controller, if that is the file system or reconfiguring the disk controller, if that is
an option. If write barriers are turned off, make sure the battery an option. If write barriers are turned off, make sure the battery
......
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