Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 8f6c942

Browse files
committed
doc: Suggest logical replication more prominently for upgrading
The previous wording suggested only Slony, and there are more options available.
1 parent bdc643e commit 8f6c942

File tree

1 file changed

+10
-3
lines changed

1 file changed

+10
-3
lines changed

doc/src/sgml/runtime.sgml

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1946,9 +1946,9 @@ pg_dumpall -p 5432 | psql -d postgres -p 5433
19461946
<title>Upgrading Data via Replication</title>
19471947

19481948
<para>
1949-
It is also possible to use certain replication methods, such as
1950-
<productname>Slony</productname>, to create a standby server with the updated version of
1951-
<productname>PostgreSQL</productname>. This is possible because Slony supports
1949+
It is also possible to use logical replication methods to create a standby
1950+
server with the updated version of <productname>PostgreSQL</productname>.
1951+
This is possible because logical replication supports
19521952
replication between different major versions of
19531953
<productname>PostgreSQL</productname>. The standby can be on the same computer or
19541954
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
19581958
of downtime for an upgrade.
19591959
</para>
19601960

1961+
<para>
1962+
This method of upgrading can be performed using the built-in logical
1963+
replication facilities as well as using external logical replication
1964+
systems such as <productname>pglogical</productname>,
1965+
<productname>Slony</productname>, <productname>Londiste</productname>, and
1966+
<productname>Bucardo</productname>.
1967+
</para>
19611968
</sect2>
19621969
</sect1>
19631970

0 commit comments

Comments
 (0)