From 9de37ea65188167b0dc0acb3ce25f031c6cb4d79 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Wed, 30 Oct 2019 13:43:16 -0400
Subject: [PATCH] relnotes: PG 12, mention change in libpq parameter parsing

Reported-by: emorley@heroku.com

Diagnosed-by: Michael Paquier

Discussion: https://postgr.es/m/157123155668.25311.9369950798665566339@wrigleys.postgresql.org

Author: Michael Paquier

Reviewed-by: me

Backpatch-through: 12 only
---
 doc/src/sgml/release-12.sgml | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/doc/src/sgml/release-12.sgml b/doc/src/sgml/release-12.sgml
index 126d6144a4..337a7a28a7 100644
--- a/doc/src/sgml/release-12.sgml
+++ b/doc/src/sgml/release-12.sgml
@@ -654,6 +654,28 @@ Author: Peter Eisentraut <peter_e@gmx.net>
      </para>
     </listitem>
 
+    <listitem>
+<!--
+Author: Michael Paquier <michael@paquier.xyz>
+2018-09-12 [e7a221797] Parse more strictly integer parameters from connection s
+-->
+
+     <para>
+      Parse libpq integer connection parameters more strictly (Fabien
+      Coelho)
+     </para> 
+
+     <para>
+      In previous releases, using an incorrect integer value for
+      connection parameters <literal>connect_timeout</literal>,
+      <literal>keepalives</literal>, <literal>keepalives_count</literal>,
+      <literal>keepalives_idle</literal>,
+      <literal>keepalives_interval</literal> and <literal>port</literal>
+      resulted in libpq either ignoring those values or failing with
+      incorrect error messages.
+     </para> 
+    </listitem>
+    
    </itemizedlist>
 
   </sect2>