aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2012-11-07 13:36:08 -0500
committerBruce Momjian <bruce@momjian.us>2012-11-07 13:36:12 -0500
commitc90dcd6d2c76402ce307b0d44958c6ca274f2c39 (patch)
treed42cdbeb8fc7f8bf18e1ecedfcad40307f6c250d /doc/src
parentadd6c3179a4d4fa3e62dd3e86a00f23303336bac (diff)
downloadpostgresql-c90dcd6d2c76402ce307b0d44958c6ca274f2c39.tar.gz
postgresql-c90dcd6d2c76402ce307b0d44958c6ca274f2c39.zip
In pg_upgrade docs, mention using base backup as part of rsync for
logical replication upgrades. Backpatch to 9.2.
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/pgupgrade.sgml5
1 files changed, 4 insertions, 1 deletions
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>