database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

Doc: Fix the ambiguity in the description of failover slots.

Browse Source 
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
This commit is contained in:
Amit Kapila
2024-08-29 08:56:52 +05:30
parent 6654bb9204
commit 9d90e2bdaf
1 changed files with 2 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
doc/src/sgml/logical-replication.sgml
View File

@ -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>