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 5523da33cf2249b8ca53162634b215fcb3ad2043..1c92e7df75140b0908095abdf8abb8fd9502ca34 100644 (file)
--- 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
    Upgrading Data via Replication
 
    
-    It is also possible to use certain replication methods, such as
-    Slony, to create a standby server with the updated version of
-    PostgreSQL.  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 PostgreSQL.
+    This is possible because logical replication supports
     replication between different major versions of
     PostgreSQL.  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.
    
 
+   
+    This method of upgrading can be performed using the built-in logical
+    replication facilities as well as using external logical replication
+    systems such as pglogical,
+    Slony, Londiste, and
+    Bucardo.
+