database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-25 21:42:33 +03:00
Code

Fix a couple of places in doc that implied there was only one sync standby.

Browse Source 
Thomas Munro
This commit is contained in:
Fujii Masao 2016-04-08 13:24:50 +09:00
parent 137805f89a
commit 8643b91ecf
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/src/sgml/high-availability.sgml
View File

@ -1086,9 +1086,10 @@ primary_slot_name = 'node_a_slot'
In the case that <varname>synchronous_commit</> is set to
<literal>remote_apply</>, the standby sends reply messages when the commit
record is replayed, making the transaction visible.
If the standby is chosen as the synchronous standby, from a priority
If the standby is chosen as a synchronous standby, from a priority
list of <varname>synchronous_standby_names</> on the primary, the reply
messages from that standby will be used to wake users waiting for
messages from that standby will be considered along with those from other
synchronous standbys to decide when to release transactions waiting for
confirmation that the commit record has been received. These parameters
allow the administrator to specify which standby servers should be
synchronous standbys. Note that the configuration of synchronous
@ -1113,10 +1114,10 @@ primary_slot_name = 'node_a_slot'
<para>
Setting <varname>synchronous_commit</> to <literal>remote_apply</> will
cause each commit to wait until the current synchronous standby reports
that it has replayed the transaction, making it visible to user queries.
In simple cases, this allows for load balancing with causal consistency
on a single hot standby.
cause each commit to wait until the current synchronous standbys report
that they have replayed the transaction, making it visible to user
queries. In simple cases, this allows for load balancing with causal
consistency.
</para>
<para>