diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml new file mode 100644 index ebc0d58..fcb0316 *** a/doc/src/sgml/ref/pgupgrade.sgml --- b/doc/src/sgml/ref/pgupgrade.sgml *************** NET STOP postgresql-9.0 *** 310,317 **** ! Streaming replication and log-shipping standby servers can remain running until ! a later step. --- 310,330 ---- ! Streaming replication and log-shipping standby servers can ! remain running until a later step. ! ! ! ! ! Verify standby servers ! ! ! 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.) *************** pg_upgrade.exe *** 404,410 **** If you have Streaming Replication () or Log-Shipping () standby servers, follow these steps to ! upgrade them (before starting any servers): --- 417,425 ---- If you have Streaming Replication () or Log-Shipping () standby servers, follow these steps to ! upgrade them. You will not be running pg_upgrade ! on the standby servers, but rather rsync. Do not ! start any servers yet. *************** pg_upgrade.exe *** 447,464 **** - - Verify standby servers - - - To prevent old standby servers from being modified, run - pg_controldata against the primary and standby - clusters and verify that the Latest checkpoint location - values match in all clusters. (This requires the standbys to be - shut down after the primary.) - - - Save configuration files --- 462,467 ----