summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian2017-06-15 16:30:02 +0000
committerBruce Momjian2017-06-15 16:30:02 +0000
commit0f33a719fdbb5d8c43839ea0d2c90cd03e2af2d2 (patch)
tree0ee233df64e563ff2e77e87b5df5d5c9f516e3e7
parent3ab7912c18b6df4d6843d0e0cd6183e7f4912cbb (diff)
docs: Fix pg_upgrade standby server upgrade docs
It was unsafe to instruct users to start/stop the server after pg_upgrade was run but before the standby servers were rsync'ed. The new instructions avoid this. RELEASE NOTES: This fix should be mentioned in the minor release notes. Reported-by: Dmitriy Sarafannikov and Sergey Burladyan Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.5, where standby server upgrade instructions first appeared
-rw-r--r--doc/src/sgml/ref/pgupgrade.sgml33
1 files changed, 15 insertions, 18 deletions
diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
index 40c978730c..5b32b75bd7 100644
--- a/doc/src/sgml/ref/pgupgrade.sgml
+++ b/doc/src/sgml/ref/pgupgrade.sgml
@@ -317,15 +317,22 @@ NET STOP postgresql-&majorversion;
</step>
<step>
- <title>Verify standby servers</title>
+ <title>Prepare for standby server upgrades</title>
<para>
- If you are upgrading Streaming Replication and Log-Shipping standby
- servers, verify that the old standby servers are caught up by running
- <application>pg_controldata</> against the old primary and standby
- clusters. Verify that the <quote>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 <xref
+ linkend="pgupgrade-step-replicas">), verify that the old standby
+ servers are caught up by running <application>pg_controldata</>
+ against the old primary and standby clusters. Verify that the
+ <quote>Latest checkpoint location</> values match in all clusters.
+ (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>
</step>
@@ -410,7 +417,7 @@ pg_upgrade.exe
</para>
</step>
- <step>
+ <step id="pgupgrade-step-replicas">
<title>Upgrade Streaming Replication and Log-Shipping standby servers</title>
<para>
@@ -472,16 +479,6 @@ pg_upgrade.exe
</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>
<title>Run <application>rsync</></title>
<para>