Hi, Fabien-san.
> From: Fabien COELHO <coelho@cri.ensmp.fr>
> As I understand the "client-side timeout" use-case, as distinct from
> network-issues-related timeouts proposed in the other patches, the point is more
> or less to deal with an overloaded server.
The main purpose of this parameter is to avoid client's waiting for DB server infinitely, not reducing the server's
burden.
This results in not waiting end-user, which is most important.
As Tsunakawa-san presented, there are similar parameters in JDBC and Oracle, so I think that this idea is valid.
> The timeout is raised because getting the result takes time, which may be simply
> because the query really takes time, and it does not imply that the server would
> not be able to process a cancel request.
You mentioned about when a SQL query is heavy, but I want to talk about when OS hang.
If OS hang occurs, the cost of cancel request processing is so high.
This is the reason why the implementation is just only disconnection without canceling.
Best regards,
---------------------
Ryohei Nagaura