RE: Timeout parameters - Mailing list pgsql-hackers

From Nagaura, Ryohei
Subject RE: Timeout parameters
Date
Msg-id EDA4195584F5064680D8130B1CA91C453F274F@G01JPEXMBYT04
Whole thread Raw
In response to RE: Timeout parameters  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses RE: Timeout parameters
List pgsql-hackers
Hi, Fabien-san.

About TCP_USER_TIMEOUT:
> From: Fabien COELHO <coelho@cri.ensmp.fr>
> 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?
Please see the previous mail[1] or current kirk-san's mail.

About socket_timeout:
> From: Fabien COELHO <coelho@cri.ensmp.fr>
> are actually finished. I cannot say that I'm thrilled by that behavior. ISTM that libpq
> should at least attempt to cancel the query 
Would you please tell me why you think so? 
If it was implemented so, timeout couldn't work when the server is so busy that can't process a cancel request.
If the client encounters such a case, how does the client stop to wait the server?
How does the client release its resources?
Socket_timeout is helpful for such clients.

I'll send patches after next week.

[1] https://www.postgresql.org/message-id/EDA4195584F5064680D8130B1CA91C453A32DB@G01JPEXMBYT04
Best regards,
---------------------
Ryohei Nagaura




pgsql-hackers by date:

Previous
From: Antonin Houska
Date:
Subject: Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS)
Next
From: Tatsuro Yamada
Date:
Subject: Re: [HACKERS] CLUSTER command progress monitor