@ -317,15 +317,22 @@ NET STOP postgresql-&majorversion;
</step>
</step>
<step>
<step>
<title>Verify standby server s</title>
<title>Prepare for standby server upgrade s</title>
<para>
<para>
If you are upgrading Streaming Replication and Log-Shipping standby
If you are upgrading standby servers (as outlined in section <xref
servers, verify that the old standby servers are caught up by running
linkend="pgupgrade-step-replicas">), verify that the old standby
<application>pg_controldata</> against the old primary and standby
servers are caught up by running <application>pg_controldata</>
clusters. Verify that the <quote>Latest checkpoint location</>
against the old primary and standby clusters. Verify that the
values match in all clusters. (There will be a mismatch if old
<quote>Latest checkpoint location</> values match in all clusters.
standby servers were shut down before the old primary.)
(There will be a mismatch if old standby servers were shut down
before the old primary.)
</para>
<para>
Also, if upgrading standby servers, change <varname>wal_level</>
to <literal>replica</> in the <filename>postgresql.conf</> file on
the new master cluster.
</para>
</para>
</step>
</step>
@ -410,7 +417,7 @@ pg_upgrade.exe
</para>
</para>
</step>
</step>
<step>
<step id="pgupgrade-step-replicas" >
<title>Upgrade Streaming Replication and Log-Shipping standby servers</title>
<title>Upgrade Streaming Replication and Log-Shipping standby servers</title>
<para>
<para>
@ -471,16 +478,6 @@ pg_upgrade.exe
</para>
</para>
</step>
</step>
<step>
<title>Start and stop the new master cluster</title>
<para>
In the new master cluster, change <varname>wal_level</> to
<literal>replica</> in the <filename>postgresql.conf</> file
and then start and stop the cluster.
</para>
</step>
<step>
<step>
<title>Run <application>rsync</></title>
<title>Run <application>rsync</></title>