From c90dcd6d2c76402ce307b0d44958c6ca274f2c39 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Wed, 7 Nov 2012 13:36:08 -0500
Subject: [PATCH] In pg_upgrade docs, mention using base backup as part of
rsync for logical replication upgrades.
Backpatch to 9.2.
---
doc/src/sgml/pgupgrade.sgml | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index 301222c55d2..998cb2fc9a5 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>
--
GitLab