From 47cacfc0f171c7794a8a953e4676db60e1fb261c Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 11 Oct 2011 17:33:20 -0400
Subject: [PATCH] Document that not backing up postmaster.pid and
postmaster.opts might help prevent pg_ctl from getting confused.
Backpatch to 9.1.
---
doc/src/sgml/backup.sgml | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
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>
--
GitLab