RE: Timeout parameters

Fabien COELHO <coelho@cri.ensmp.fr>

From: Fabien COELHO <coelho@cri.ensmp.fr>
To: "Nagaura, Ryohei" <nagaura.ryohei@jp.fujitsu.com>
Cc: "'pgsql-hackers@postgresql.org'" <pgsql-hackers@postgresql.org>, "AYahorau@ibagroup.eu" <AYahorau@ibagroup.eu>
Date: 2018-12-26T07:40:00Z
Lists: pgsql-hackers
Hello Ryohei,

>>>> 4. The client wants to close the connection while leaving the job to
>>>> the server.
>>>> In this case, "statement_timeout" can't satisfy at line 4.
>>
>> Why?
>> ISTM that "leaving the job" to the server with a client-side connection
>> closed is basically an abort, no different from what server-side
>> "statement_timeout" already provides?
> "while leaving the job to the server" means that "while the server continue the job".
> # Sorry for the inappropriate explanation.
> I understand that "statement_timeout" won't.

I still do not understand the use-case specifics: for me, aborting the 
connection, or a softer cancelling the statement, will result in the 
server stopping the statement, so the server does NOT "continue the job", 
so I still do not see how it really differs from the server-side 
statement_timeout setting.

-- 
Fabien.


Commits

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