From f9951252dbd86391ab3a9bcba99f4e9f13e311a6 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 10 Jul 2012 23:08:19 -0400
Subject: [PATCH] Document that Log-Shipping Standby Servers cannot be upgraded
by pg_upgrade.
Backpatch to 9.2.
---
doc/src/sgml/pgupgrade.sgml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index 30f45441978..cffcebb3070 100644
--- a/doc/src/sgml/pgupgrade.sgml
+++ b/doc/src/sgml/pgupgrade.sgml
@@ -517,6 +517,12 @@ psql --username postgres --file script.sql postgres
<literal>-d /real-data-directory -o '-D /configuration-directory'</>.
</para>
+ <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.
+ </para>
+
<para>
If you want to use link mode and you do not want your old cluster
to be modified when the new cluster is started, make a copy of the
--
GitLab