diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
index bbb606d1caa..8b05b22c986 100644
--- a/doc/src/sgml/ref/pgupgrade.sgml
+++ b/doc/src/sgml/ref/pgupgrade.sgml
@@ -317,15 +317,22 @@ NET STOP postgresql-9.0
- Verify standby servers
+ Prepare for standby server upgrades
- If you are upgrading Streaming Replication and Log-Shipping standby
- servers, verify that the old standby servers are caught up by running
- pg_controldata> against the old primary and standby
- clusters. Verify that the Latest checkpoint location>
- values match in all clusters. (There will be a mismatch if old
- standby servers were shut down before the old primary.)
+ If you are upgrading standby servers (as outlined in section ), verify that the old standby
+ servers are caught up by running pg_controldata>
+ against the old primary and standby clusters. Verify that the
+ Latest checkpoint location> values match in all clusters.
+ (There will be a mismatch if old standby servers were shut down
+ before the old primary.)
+
+
+
+ Also, if upgrading standby servers, change wal_level>
+ to replica> in the postgresql.conf> file on
+ the new master cluster.
@@ -410,7 +417,7 @@ pg_upgrade.exe
-
+
Upgrade Streaming Replication and Log-Shipping standby servers
@@ -471,16 +478,6 @@ pg_upgrade.exe
-
- Start and stop the new master cluster
-
-
- In the new master cluster, change wal_level> to
- replica> in the postgresql.conf> file
- and then start and stop the cluster.
-
-
-
Run rsync>