Re: libpq: Fix wrong connection status on invalid "connect_timeout"

2019-10-20 Thread Michael Paquier
On Fri, Oct 18, 2019 at 02:01:23PM +0200, Lars Kanis wrote: > Am 18.10.19 um 05:06 schrieb Michael Paquier: >> So attached is a patch to skip trailing whitespaces as well, >> which also fixes the issue with ECPG. I have refactored the parsing >> logic a bit while on it. The comment at the top of

Re: libpq: Fix wrong connection status on invalid "connect_timeout"

2019-10-18 Thread Lars Kanis
Am 18.10.19 um 05:06 schrieb Michael Paquier: > So attached is a patch to skip trailing whitespaces as well, > which also fixes the issue with ECPG. I have refactored the parsing > logic a bit while on it. The comment at the top of parse_int_param() > needs to be reworked a bit more. I tested

Re: libpq: Fix wrong connection status on invalid "connect_timeout"

2019-10-18 Thread Lars Kanis
Am 18.10.19 um 05:06 schrieb Michael Paquier: > So attached is a patch to skip trailing whitespaces as well, > which also fixes the issue with ECPG. I have refactored the parsing > logic a bit while on it. The comment at the top of parse_int_param() > needs to be reworked a bit more. I tested

Re: libpq: Fix wrong connection status on invalid "connect_timeout"

2019-10-18 Thread Lars Kanis
Am 18.10.19 um 05:06 schrieb Michael Paquier: > So attached is a patch to skip trailing whitespaces as well, > which also fixes the issue with ECPG. I have refactored the parsing > logic a bit while on it. The comment at the top of parse_int_param() > needs to be reworked a bit more. I tested

Re: libpq: Fix wrong connection status on invalid "connect_timeout"

2019-10-17 Thread Michael Paquier
On Thu, Oct 17, 2019 at 10:10:17PM +0200, Lars Kanis wrote: > That's why I changed connectDBComplete() only, instead of setting the > status directly in parse_int_param(). Yes, you shouldn't do that as the keepalive parameters and tcp_user_timeout have some specific handling when it comes to

Re: libpq: Fix wrong connection status on invalid "connect_timeout"

2019-10-17 Thread Lars Kanis
I verified that all other integer parameters properly set CONNECTION_BAD in case of invalid values. These are: * port * keepalives_idle * keepalives_interval * keepalives_count * tcp_user_timeout That's why I changed connectDBComplete() only, instead of setting the status directly in

libpq: Fix wrong connection status on invalid "connect_timeout"

2019-10-17 Thread Lars Kanis
Greetings, libpq since PostgreSQL-12 has stricter checks for integer values in connection parameters. They were introduced by commit https://github.com/postgres/postgres/commit/e7a2217978d9cbb2149bfcb4ef1e45716cfcbefb . However in case of "connect_timeout" such an invalid integer value leads to