aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2011-10-11 17:33:20 -0400
committerBruce Momjian <bruce@momjian.us>2011-10-11 17:33:20 -0400
commit47cacfc0f171c7794a8a953e4676db60e1fb261c (patch)
treec0ba34e544380bfeee73418a5ae9d40a599467f5
parent600d3206d1b3f8b540397b79905486a536ac7f78 (diff)
downloadpostgresql-47cacfc0f171c7794a8a953e4676db60e1fb261c.tar.gz
postgresql-47cacfc0f171c7794a8a953e4676db60e1fb261c.zip
Document that not backing up postmaster.pid and postmaster.opts might
help prevent pg_ctl from getting confused. Backpatch to 9.1.
-rw-r--r--doc/src/sgml/backup.sgml6
1 files changed, 5 insertions, 1 deletions
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>