Horton

RE: Timeout parameters

Fabien COELHO <coelho@cri.ensmp.fr>

View thread View on postgr.es
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: "Nagaura, Ryohei" <nagaura.ryohei@jp.fujitsu.com>
Cc: "Jamison, Kirk" <k.jamison@jp.fujitsu.com>, "Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>, 'Michael Paquier' <michael@paquier.xyz>, "AYahorau@ibagroup.eu" <AYahorau@ibagroup.eu>, "'pgsql-hackers@postgresql.org'" <pgsql-hackers@postgresql.org>, "MikalaiKeida@ibagroup.eu" <MikalaiKeida@ibagroup.eu>
Date: 2019-03-03T07:09:07Z
Lists: pgsql-hackers 
> About the tcp_user_timeout libpq parameter v8.

Basically same thing about the tcp_user_timeout guc v8, especially: do you 
have any advice about how I can test the feature, i.e. trigger a timeout?

> Patch applies & compiles cleanly. Global check is ok, although there are no 
> specific tests.
>
> Documentation English can be improved. Could a native speaker help, please?
>
> ISTM that the documentation both states that it works and does not work on 
> Windows. One assertion must be false.
>
> Syntax error, eg "tcp_user_timeout=2bad", are detected, good.
>
> I could not really test the feature, i.e. I could not trigger a timeout. Do 
> you have a suggestion on how to test it?


-- 
Fabien.

Commits

  1. Add support TCP user timeout in libpq and the backend server