From: Bruce Momjian <bruce@momjian.us>
Date: Fri, 24 Dec 2010 16:32:52 +0000 (-0500)
Subject: Backpatch to 9.0 a doc mention that a BBU does not prevent partial page
X-Git-Tag: REL9_0_3~27
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=c47458529533bc88e34778818a4ce7d5c309d7a8;p=thirdparty%2Fpostgresql.git

Backpatch to 9.0 a doc mention that a BBU does not prevent partial page
writes.
---

diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
index 54fcf93954d..e212ddf16c0 100644
--- a/doc/src/sgml/wal.sgml
+++ b/doc/src/sgml/wal.sgml
@@ -167,10 +167,12 @@
    <productname>PostgreSQL</> periodically writes full page images to
    permanent WAL storage <emphasis>before</> modifying the actual page on
    disk. By doing this, during crash recovery <productname>PostgreSQL</> can
-   restore partially-written pages from WAL.  If you have a battery-backed disk
-   controller or file-system software that prevents partial page writes
-   (e.g., ZFS), you can safely turn off this page imaging by turning off the
-   <xref linkend="guc-full-page-writes"> parameter.
+   restore partially-written pages from WAL.  If you have file-system software
+   that prevents partial page writes (e.g., ZFS),  you can turn off
+   this page imaging by turning off the <xref
+   linkend="guc-full-page-writes"> parameter. Battery-Backed Unit
+   (BBU) disk controllers do not prevent partial page writes unless
+   they guarantee that data is written to the BBU as full (8kB) pages.
   </para>
  </sect1>