From: Peter Eisentraut <peter_e@gmx.net>
Date: Tue, 12 Jun 2018 01:34:32 +0000 (-0400)
Subject: doc: Suggest logical replication more prominently for upgrading
X-Git-Tag: REL_11_BETA2~67
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=8f6c94272c485bb812aebe063fc412326a17b880;p=postgresql

doc: Suggest logical replication more prominently for upgrading

The previous wording suggested only Slony, and there are more options
available.
---

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 5523da33cf..1c92e7df75 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1946,9 +1946,9 @@ pg_dumpall -p 5432 | psql -d postgres -p 5433
    <title>Upgrading Data via Replication</title>
 
    <para>
-    It is also possible to use certain replication methods, such as
-    <productname>Slony</productname>, to create a standby server with the updated version of
-    <productname>PostgreSQL</productname>.  This is possible because Slony supports
+    It is also possible to use logical replication methods to create a standby
+    server with the updated version of <productname>PostgreSQL</productname>.
+    This is possible because logical replication supports
     replication between different major versions of
     <productname>PostgreSQL</productname>.  The standby can be on the same computer or
     a different computer.  Once it has synced up with the master server
@@ -1958,6 +1958,13 @@ pg_dumpall -p 5432 | psql -d postgres -p 5433
     of downtime for an upgrade.
    </para>
 
+   <para>
+    This method of upgrading can be performed using the built-in logical
+    replication facilities as well as using external logical replication
+    systems such as <productname>pglogical</productname>,
+    <productname>Slony</productname>, <productname>Londiste</productname>, and
+    <productname>Bucardo</productname>.
+   </para>
   </sect2>
  </sect1>