summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael Paquier2019-07-24 07:02:28 +0000
committerMichael Paquier2019-07-24 07:02:28 +0000
commit2315a261de159e843cf970714ddd6042a9a8a23f (patch)
treee59a646f643444e339cb208c844ad3e1b2e77266
parent4a25ed16400c01fb64c23d2d6f413af95b4e28f8 (diff)
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
-rw-r--r--doc/src/sgml/ref/pg_receivexlog.sgml4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/ref/pg_receivexlog.sgml b/doc/src/sgml/ref/pg_receivexlog.sgml
index 4cfc490e0a8..ab17966d1c1 100644
--- a/doc/src/sgml/ref/pg_receivexlog.sgml
+++ b/doc/src/sgml/ref/pg_receivexlog.sgml
@@ -54,11 +54,11 @@ PostgreSQL documentation
The option <option>--synchronous</> must be specified to flush WAL data
in real time. Since <application>pg_receivexlog</application> does not
apply WAL, you should not allow it to become a synchronous standby when
- <xref linkend="guc-synchronous-commit"/> equals
+ <xref linkend="guc-synchronous-commit"> equals
<literal>remote_apply</literal>. If it does, it will appear to be a
standby that never catches up, and will cause transaction commits to
block. To avoid this, you should either configure an appropriate value
- for <xref linkend="guc-synchronous-standby-names"/>, or specify
+ for <xref linkend="guc-synchronous-standby-names">, or specify
<varname>application_name</varname> for
<application>pg_receivexlog</application> that does not match it, or
change the value of <varname>synchronous_commit</varname> to