From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 11 Oct 2011 21:33:21 +0000 (-0400)
Subject: Document that not backing up postmaster.pid and postmaster.opts might
X-Git-Tag: REL9_1_2~80
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=35db9d0ab8a81470b2be62728105cfa36e26e56c;p=thirdparty%2Fpostgresql.git

Document that not backing up postmaster.pid and postmaster.opts might
help prevent pg_ctl from getting confused.

Backpatch to 9.1.
---

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index b8daedcbb6e..737355a911d 100644
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -869,7 +869,11 @@ SELECT pg_stop_backup();
     of mistakes when restoring.  This is easy to arrange if
     <filename>pg_xlog/</> is a symbolic link pointing to someplace outside
     the cluster directory, which is a common setup anyway for performance
-    reasons.
+    reasons.  You might also want to exclude <filename>postmaster.pid</>
+    and <filename>postmaster.opts</>, which record information
+    about the running <application>postmaster</>, not about the
+    <application>postmaster</> which will eventually use this backup.
+    (These files can confuse <application>pg_ctl</>.)
    </para>
 
    <para>