diff options
| author | Peter Eisentraut | 2018-06-12 01:34:32 +0000 |
|---|---|---|
| committer | Peter Eisentraut | 2018-06-12 01:34:32 +0000 |
| commit | 8f6c94272c485bb812aebe063fc412326a17b880 (patch) | |
| tree | 84fcf76cd7ec9e57e6a0505ab47d4c4ec7bc549c | |
| parent | bdc643e5e46f84d55d989980e4ff5f8e2da103c6 (diff) | |
doc: Suggest logical replication more prominently for upgrading
The previous wording suggested only Slony, and there are more options
available.
| -rw-r--r-- | doc/src/sgml/runtime.sgml | 13 |
1 files changed, 10 insertions, 3 deletions
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index 5523da33cf2..1c92e7df751 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> |