Skip to content

Commit baf21b9

Browse files
committed
doc: Fix minor markup issue
There shouldn't be a line break between two adjacent tags, because that will appear as whitespace in the output. (The rendering engine might in turn collapse that whitespace away, so it might not actually make a difference, but it's more correct this way.)
1 parent 7b34740 commit baf21b9

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

doc/src/sgml/config.sgml

+6-5
Original file line numberDiff line numberDiff line change
@@ -3212,9 +3212,9 @@ include_dir 'conf.d'
32123212
The synchronous standbys will be those whose names appear
32133213
in this list, and
32143214
that are both currently connected and streaming data in real-time
3215-
(as shown by a state of <literal>streaming</literal> in the
3216-
<link linkend="pg-stat-replication-view">
3217-
<literal>pg_stat_replication</literal></link> view).
3215+
(as shown by a state of <literal>streaming</literal> in the <link
3216+
linkend="pg-stat-replication-view"><literal>pg_stat_replication</literal></link>
3217+
view).
32183218
Specifying more than one synchronous standby can allow for very high
32193219
availability and protection against data loss.
32203220
</para>
@@ -3461,8 +3461,9 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="
34613461
Specifies the minimum frequency for the WAL receiver
34623462
process on the standby to send information about replication progress
34633463
to the primary or upstream standby, where it can be seen using the
3464-
<link linkend="pg-stat-replication-view">
3465-
<literal>pg_stat_replication</literal></link> view. The standby will report
3464+
<link
3465+
linkend="pg-stat-replication-view"><literal>pg_stat_replication</literal></link>
3466+
view. The standby will report
34663467
the last write-ahead log location it has written, the last position it
34673468
has flushed to disk, and the last position it has applied.
34683469
This parameter's

0 commit comments

Comments
 (0)