Commitba7359d

committed

Fix build of documentation

Oversight in1c42346, which has incorrectly shaped a <xref> markup.Only v10 and v9.6 got broken.Reported-by: Stefan KaltenbrunnerDiscussion:https://postgr.es/m/675cde90-a8dc-faeb-4701-d35a89ee06a2@kaltenbrunner.cc

1 parent1c42346 commitba7359dCopy full SHA for ba7359d

File tree

-2

lines changed

-2

lines changed

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -54,11 +54,11 @@ PostgreSQL documentation`
`54`	`54`	`The option <option>--synchronous</> must be specified to flush WAL data`
`55`	`55`	`in real time. Since <application>pg_receivewal</application> does not`
`56`	`56`	`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`
`58`	`58`	`<literal>remote_apply</literal>. If it does, it will appear to be a`
`59`	`59`	`standby that never catches up, and will cause transaction commits to`
`60`	`60`	`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`
`62`	`62`	`<varname>application_name</varname> for`
`63`	`63`	`<application>pg_receivewal</application> that does not match it, or`
`64`	`64`	`change the value of <varname>synchronous_commit</varname> to`

Comments

(0)