RE: Timeout parameters

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: "Nagaura, Ryohei" <nagaura(dot)ryohei(at)jp(dot)fujitsu(dot)com>
Cc: "Jamison, Kirk" <k(dot)jamison(at)jp(dot)fujitsu(dot)com>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, 'Michael Paquier' <michael(at)paquier(dot)xyz>, "AYahorau(at)ibagroup(dot)eu" <AYahorau(at)ibagroup(dot)eu>, "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org>, "MikalaiKeida(at)ibagroup(dot)eu" <MikalaiKeida(at)ibagroup(dot)eu>
Subject: RE: Timeout parameters
Date: 2019-03-03 07:09:07
Message-ID: alpine.DEB.2.21.1903030758490.8095@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
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?


In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2019-03-03 08:06:20 Re: libpq environment variables in the server
Previous Message Fabien COELHO 2019-03-03 06:58:26 Re: Online verification of checksums