diff options
author | Amit Kapila <akapila@postgresql.org> | 2024-08-29 08:45:41 +0530 |
---|---|---|
committer | Amit Kapila <akapila@postgresql.org> | 2024-08-29 08:45:41 +0530 |
commit | 135007a1008c11e849036692ffe180dd7d4b5107 (patch) | |
tree | 63911c608647c9a952199c07feb0a9cb3b4ece9b | |
parent | 0be079ec9706eb80f0142b0d7deba245024acdce (diff) | |
download | postgresql-135007a1008c11e849036692ffe180dd7d4b5107.tar.gz postgresql-135007a1008c11e849036692ffe180dd7d4b5107.zip |
Doc: Fix the ambiguity in the description of failover slots.
The failover slots ensure a seamless transition of a subscriber after the
standby is promoted. But the docs for it also explain the behavior of
asynchronous replication which can confuse the readers.
Reported-by: Masahiro Ikeda
Backpatch-through: 17
Discussion: https://postgr.es/m/OS3PR01MB6390B660F4198BB9745E0526B18B2@OS3PR01MB6390.jpnprd01.prod.outlook.com
-rw-r--r-- | doc/src/sgml/logical-replication.sgml | 7 |
1 files changed, 2 insertions, 5 deletions
diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml index a23a3d57e2b..88b2491e09b 100644 --- a/doc/src/sgml/logical-replication.sgml +++ b/doc/src/sgml/logical-replication.sgml @@ -701,10 +701,7 @@ ALTER SUBSCRIPTION <link linkend="sql-createsubscription-params-with-failover"><literal>failover</literal></link> parameter ensures a seamless transition of those subscriptions after the standby is promoted. They can continue subscribing to publications on the - new primary server without losing data. Note that in the case of - asynchronous replication, there remains a risk of data loss for transactions - committed on the former primary server but have yet to be replicated to the new - primary server. + new primary server. </para> <para> @@ -791,7 +788,7 @@ test_standby=# SELECT slot_name, (synced AND NOT temporary AND NOT conflicting) If all the slots are present on the standby server and the result (<literal>failover_ready</literal>) of the above SQL query is true, then existing subscriptions can continue subscribing to publications now on the - new primary server without losing data. + new primary server. </para> </sect1> |