@@ -310,8 +310,21 @@ NET STOP postgresql-9.0
310310 </para>
311311
312312 <para>
313- Streaming replication and log-shipping standby servers can remain running until
314- a later step.
313+ Streaming replication and log-shipping standby servers can
314+ remain running until a later step.
315+ </para>
316+ </step>
317+
318+ <step>
319+ <title>Verify standby servers</title>
320+
321+ <para>
322+ If you are upgrading Streaming Replication and Log-Shipping standby
323+ servers, verify that the old standby servers are caught up by running
324+ <application>pg_controldata</> against the old primary and standby
325+ clusters. Verify that the <quote>Latest checkpoint location</>
326+ values match in all clusters. (There will be a mismatch if old
327+ standby servers were shut down before the old primary.)
315328 </para>
316329 </step>
317330
@@ -404,7 +417,9 @@ pg_upgrade.exe
404417 If you have Streaming Replication (<xref
405418 linkend="streaming-replication">) or Log-Shipping (<xref
406419 linkend="warm-standby">) standby servers, follow these steps to
407- upgrade them (before starting any servers):
420+ upgrade them. You will not be running <application>pg_upgrade</>
421+ on the standby servers, but rather <application>rsync</>. Do not
422+ start any servers yet.
408423 </para>
409424
410425 <substeps>
@@ -447,18 +462,6 @@ pg_upgrade.exe
447462 </para>
448463 </step>
449464
450- <step>
451- <title>Verify standby servers</title>
452-
453- <para>
454- To prevent old standby servers from being modified, run
455- <application>pg_controldata</> against the primary and standby
456- clusters and verify that the <quote>Latest checkpoint location</>
457- values match in all clusters. (This requires the standbys to be
458- shut down after the primary.)
459- </para>
460- </step>
461-
462465 <step>
463466 <title>Save configuration files</title>
464467
0 commit comments