diff options
| author | Amit Kapila <akapila@postgresql.org> | 2024-08-29 08:56:52 +0530 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2024-08-29 08:56:52 +0530 |
| commit | 9d90e2bdafbdeba037aa4fee3febe9f48201bf74 (patch) | |
| tree | 4ab83802cd636e809491f4977749e19f58096481 /doc/src | |
| parent | 6654bb92047b37cee053cedd6fa1829841b2ad8e (diff) | |
| download | postgresql-9d90e2bdafbdeba037aa4fee3febe9f48201bf74.tar.gz postgresql-9d90e2bdafbdeba037aa4fee3febe9f48201bf74.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
Diffstat (limited to 'doc/src')
| -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 bee7e02983b..bc095d01c00 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> |