summaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorBruce Momjian2012-07-11 03:08:19 +0000
committerBruce Momjian2012-07-11 03:08:19 +0000
commitf9951252dbd86391ab3a9bcba99f4e9f13e311a6 (patch)
treeaa29083e461ba4d3f49a12887e9f9badd0424ff7 /doc/src
parent01215d61a7b162ca441c5bc0312550f2d88fddb2 (diff)
Document that Log-Shipping Standby Servers cannot be upgraded by
pg_upgrade. Backpatch to 9.2.
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/pgupgrade.sgml6
1 files changed, 6 insertions, 0 deletions
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
@@ -518,6 +518,12 @@ psql --username postgres --file script.sql postgres
</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
old cluster and upgrade that in link mode. To make a valid copy