From: Bruce Momjian <bruce@momjian.us>
Date: Wed, 7 Nov 2012 18:36:08 +0000 (-0500)
Subject: In pg_upgrade docs, mention using base backup as part of rsync for
X-Git-Tag: REL9_3_BETA1~737
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=c90dcd6d2c76402ce307b0d44958c6ca274f2c39;p=postgresql

In pg_upgrade docs, mention using base backup as part of rsync for
logical replication upgrades.

Backpatch to 9.2.
---

diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index 301222c55d..998cb2fc9a 100644
--- a/doc/src/sgml/pgupgrade.sgml
+++ b/doc/src/sgml/pgupgrade.sgml
@@ -529,7 +529,10 @@ psql --username postgres --file script.sql postgres
   <para>
    A Log-Shipping Standby Server (<xref linkend="warm-standby">) cannot
    be upgraded because the server must allow writes.  The simplest way
-   is to upgrade the primary and use rsync to rebuild the standbys.
+   is to upgrade the primary and use <command>rsync</> to rebuild the
+   standbys.  You can run <command>rsync</> while the primary is down,
+   or as part of a base backup (<xref linkend="backup-base-backup">)
+   which overwrites the old standby cluster.
   </para>
 
   <para>