Skip to content

Commit ba7359d

Browse files
committed
Fix build of documentation
Oversight in 1c42346, which has incorrectly shaped a <xref> markup. Only v10 and v9.6 got broken. Reported-by: Stefan Kaltenbrunner Discussion: https://postgr.es/m/675cde90-a8dc-faeb-4701-d35a89ee06a2@kaltenbrunner.cc
1 parent 1c42346 commit ba7359d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

doc/src/sgml/ref/pg_receivewal.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -54,11 +54,11 @@ PostgreSQL documentation
5454
The option <option>--synchronous</> must be specified to flush WAL data
5555
in real time. Since <application>pg_receivewal</application> does not
5656
apply WAL, you should not allow it to become a synchronous standby when
57-
<xref linkend="guc-synchronous-commit"/> equals
57+
<xref linkend="guc-synchronous-commit"> equals
5858
<literal>remote_apply</literal>. If it does, it will appear to be a
5959
standby that never catches up, and will cause transaction commits to
6060
block. To avoid this, you should either configure an appropriate value
61-
for <xref linkend="guc-synchronous-standby-names"/>, or specify
61+
for <xref linkend="guc-synchronous-standby-names">, or specify
6262
<varname>application_name</varname> for
6363
<application>pg_receivewal</application> that does not match it, or
6464
change the value of <varname>synchronous_commit</varname> to

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy