Commit9de37ea

committed

relnotes: PG 12, mention change in libpq parameter parsing

Reported-by: emorley@heroku.comDiagnosed-by: Michael PaquierDiscussion:https://postgr.es/m/157123155668.25311.9369950798665566339@wrigleys.postgresql.orgAuthor: Michael PaquierReviewed-by: meBackpatch-through: 12 only

1 parentd4b5206 commit9de37eaCopy full SHA for 9de37ea

File tree

+22

-0

lines changed

+22

-0

lines changed

Lines changed: 22 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -654,6 +654,28 @@ Author: Peter Eisentraut <peter_e@gmx.net>`
`654`	`654`	`</para>`
`655`	`655`	`</listitem>`
`656`	`656`
	`657`	`+ <listitem>`
	`658`	`+<!--`
	`659`	`+Author: Michael Paquier <michael@paquier.xyz>`
	`660`	`+2018-09-12 [e7a221797] Parse more strictly integer parameters from connection s`
	`661`	`+-->`
	`662`	`+`
	`663`	`+ <para>`
	`664`	`+ Parse libpq integer connection parameters more strictly (Fabien`
	`665`	`+ Coelho)`
	`666`	`+ </para>`
	`667`	`+`
	`668`	`+ <para>`
	`669`	`+ In previous releases, using an incorrect integer value for`
	`670`	`+ connection parameters <literal>connect_timeout</literal>,`
	`671`	`+ <literal>keepalives</literal>, <literal>keepalives_count</literal>,`
	`672`	`+ <literal>keepalives_idle</literal>,`
	`673`	`+ <literal>keepalives_interval</literal> and <literal>port</literal>`
	`674`	`+ resulted in libpq either ignoring those values or failing with`
	`675`	`+ incorrect error messages.`
	`676`	`+ </para>`
	`677`	`+ </listitem>`
	`678`	`+`
`657`	`679`	`</itemizedlist>`
`658`	`680`
`659`	`681`	`</sect2>`

Comments

(0)