From d854c7dc6c59874ea6086f7bee29edd45394d0ae Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Fri, 30 Nov 2012 22:14:17 -0500
Subject: [PATCH] dummy commit

---
 doc/src/sgml/config.sgml | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index b56070b0fb..fa8de0161e 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1696,6 +1696,15 @@ include 'filename'
         turning off <varname>fsync</varname>.
        </para>
 
+       <para>
+        For reliable recovery when changing a cluster from
+        <varname>fsync</varname> off to on, it is necessary to force all
+        modified buffers in the kernel to durable storage.  This can be
+        done while the cluster is shutdown or while fsync is on by running
+        <command>initdb --sync-only</command>, running <command>sync</>,
+        unmounting the file system, or rebooting the server.
+       </para>
+
        <para>
         In many situations, turning off <xref linkend="guc-synchronous-commit">
         for noncritical transactions can provide much of the potential
-- 
2.40.0