From 520c41b5269e6e1f541881e1c3f27eccdb640937 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 15 Jan 2009 00:34:25 +0000
Subject: [PATCH] Add documentation mention that full page writes have to be
 enabled for full pages to be restored during recovery.

Per private report from Michael Renner
---
 doc/src/sgml/wal.sgml | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
index e5750b62dc..70675974a2 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.57 2008/12/18 22:34:21 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.58 2009/01/15 00:34:25 momjian Exp $ -->
 
 <chapter id="wal">
  <title>Reliability and the Write-Ahead Log</title>
@@ -543,7 +543,8 @@
    then the checkpoint record; then it performs the REDO operation by
    scanning forward from the log position indicated in the checkpoint
    record.  Because the entire content of data pages is saved in the
-   log on the first page modification after a checkpoint, all pages
+   log on the first page modification after a checkpoint (assuming
+   <xref linkend="guc-full-page-writes"> is not disabled), all pages
    changed since the checkpoint will be restored to a consistent
    state.
   </para>
-- 
2.11.0