summaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/config.sgml27
1 files changed, 14 insertions, 13 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index dce1daa73ae..b2c5e4d5dd2 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -2983,7 +2983,7 @@ include_dir 'conf.d'
</term>
<listitem>
<para>
- Specifies a list of standby names that can support
+ Specifies a list of standby servers that can support
<firstterm>synchronous replication</>, as described in
<xref linkend="synchronous-replication">.
There will be one or more active synchronous standbys;
@@ -2991,7 +2991,7 @@ include_dir 'conf.d'
these standby servers confirm receipt of their data.
The synchronous standbys will be those whose names appear
earlier in this list, and
- that is both currently connected and streaming data in real-time
+ that are both currently connected and streaming data in real-time
(as shown by a state of <literal>streaming</literal> in the
<link linkend="monitoring-stats-views-table">
<literal>pg_stat_replication</></link> view).
@@ -3002,7 +3002,7 @@ include_dir 'conf.d'
Specifying more than one standby name can allow very high availability.
</para>
<para>
- This parameter specifies a list of standby servers by using
+ This parameter specifies a list of standby servers using
either of the following syntaxes:
<synopsis>
<replaceable class="parameter">num_sync</replaceable> ( <replaceable class="parameter">standby_name</replaceable> [, ...] )
@@ -3013,17 +3013,17 @@ include_dir 'conf.d'
wait for replies from,
and <replaceable class="parameter">standby_name</replaceable>
is the name of a standby server. For example, a setting of
- <literal>'3 (s1, s2, s3, s4)'</> makes transaction commits wait
- until their WAL records are received by three higher priority standbys
+ <literal>3 (s1, s2, s3, s4)</> makes transaction commits wait
+ until their WAL records are received by three higher-priority standbys
chosen from standby servers <literal>s1</>, <literal>s2</>,
<literal>s3</> and <literal>s4</>.
</para>
<para>
The second syntax was used before <productname>PostgreSQL</>
version 9.6 and is still supported. It's the same as the first syntax
- with <replaceable class="parameter">num_sync</replaceable>=1.
- For example, both settings of <literal>'1 (s1, s2)'</> and
- <literal>'s1, s2'</> have the same meaning; either <literal>s1</>
+ with <replaceable class="parameter">num_sync</replaceable> equal to 1.
+ For example, <literal>1 (s1, s2)</> and
+ <literal>s1, s2</> have the same meaning: either <literal>s1</>
or <literal>s2</> is chosen as a synchronous standby.
</para>
<para>
@@ -3039,11 +3039,12 @@ include_dir 'conf.d'
</para>
<note>
<para>
- The <replaceable class="parameter">standby_name</replaceable>
- must be enclosed in double quotes if a comma (<literal>,</>),
- a double quote (<literal>"</>), <!-- " font-lock sanity -->
- a left parentheses (<literal>(</>), a right parentheses (<literal>)</>)
- or a space is used in the name of a standby server.
+ Each <replaceable class="parameter">standby_name</replaceable>
+ should have the form of a valid SQL identifier, unless it
+ is <literal>*</>. You can use double-quoting if necessary. But note
+ that <replaceable class="parameter">standby_name</replaceable>s are
+ compared to standby application names case-insensitively, whether
+ double-quoted or not.
</para>
</note>
<para>