aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2017-09-13 09:22:18 -0400
committerBruce Momjian <bruce@momjian.us>2017-09-13 09:22:18 -0400
commit6dffdcfeef934eb21b8a767d8be11ec33ccb56ed (patch)
treecec20a269946b86a8d02dd3a0f230a0af81a260b
parentaaa4faa7a00cb85322e570f2d148a51b95b847c4 (diff)
downloadpostgresql-6dffdcfeef934eb21b8a767d8be11ec33ccb56ed.tar.gz
postgresql-6dffdcfeef934eb21b8a767d8be11ec33ccb56ed.zip
docs: adjust "link mode" mention in pg_upgrade streaming steps
Backpatch-through: 9.5
-rw-r--r--doc/src/sgml/ref/pgupgrade.sgml14
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
index ab2defe0396..60011d8167a 100644
--- a/doc/src/sgml/ref/pgupgrade.sgml
+++ b/doc/src/sgml/ref/pgupgrade.sgml
@@ -421,14 +421,14 @@ pg_upgrade.exe
<title>Upgrade Streaming Replication and Log-Shipping standby servers</title>
<para>
- If you have Streaming Replication (see <xref
+ If you used link mode and have Streaming Replication (see <xref
linkend="streaming-replication">) or Log-Shipping (see <xref
- linkend="warm-standby">) standby servers, and used link mode,
- follow these steps to upgrade them. You will not be running
- <application>pg_upgrade</> on the standby servers, but rather
- <application>rsync</> on the primary. Do not start any servers yet.
- If you did <emphasis>not</> use link mode, skip the instructions in
- this section and simply recreate the standby servers.
+ linkend="warm-standby">) standby servers, follow these steps to
+ upgrade them. You will not be running <application>pg_upgrade</> on
+ the standby servers, but rather <application>rsync</> on the primary.
+ Do not start any servers yet. If you did <emphasis>not</> use link
+ mode, skip the instructions in this section and simply recreate the
+ standby servers.
</para>
<substeps>