From ba95a6933632410d103d6f17cd3bc1adf92a08f9 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Wed, 22 May 2019 10:54:40 -0400
Subject: [PATCH] doc:  PG 12 relnotes,  correct recovery_target* variable
 mention

Clarify new restriction on recovery_target* variables.

Reported-by: Gaby Schilders

Discussion: reported via chat
---
 doc/src/sgml/release-12.sgml | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/doc/src/sgml/release-12.sgml b/doc/src/sgml/release-12.sgml
index 10b3ed56f7..dcce866892 100644
--- a/doc/src/sgml/release-12.sgml
+++ b/doc/src/sgml/release-12.sgml
@@ -127,15 +127,20 @@ Author: Peter Eisentraut <peter_e@gmx.net>
 -->
 
      <para>
-      Do not allow multiple different <link
+      Do not allow multiple conflicting <link
       linkend="runtime-config-wal-recovery-target"><varname>recovery_target</varname>*</link>
       specifications (Peter Eisentraut)
      </para>
 
      <para>
-      Previously, multiple different <varname>recovery_target</varname>*
-      variables could be specified, and the last one specified was
-      honored.  Now, only one can be specified, though the same one can
+      Specifically, only allow one of <xref
+      linkend="guc-recovery-target"/>, <xref
+      linkend="guc-recovery-target-lsn"/>,
+      <xref linkend="guc-recovery-target-name"/>,
+      <xref linkend="guc-recovery-target-time"/>, <xref
+      linkend="guc-recovery-target-xid"/>.  Previously, multiple different
+      instances of the variables above could be specified, and the last one
+      was honored.  Now, only one can be specified, though the same one can
       be specified multiple times and the last specification is honored.
      </para>
     </listitem>
-- 
2.40.0