RE: Timeout parameters

On Friday, February 22, 2019 9:46 AM (GMT+9), Tsunakawa, Takayuki wrote:

> > Terminate any session that has been idle for more than the
> > specified number of seconds to prevent client from infinite
> > waiting for server due to dead connection. This can be used both as a
> > brute force global query timeout and detecting network problems.
> > A value of zero (the default) turns this off.
>
> Looks better than the original one. However,
>
> * The unit is not millisecond, but second.
> * Doesn't restart the session.
> * Choose words that better align with the existing libpq parameters.
> e.g. "connection" should be used instead of "session" as in
> keepalive_xxx parameters, because there's not a concept of database
> session at socket level.
> * Indicate that the timeout is for individual socket operations.

My bad. I was looking at the wrong documentations, so seconds should be used.
I guess we should just choose socket_timeout as parameter name.

socket_timeout (integer)

Terminate any connection that has been inactive for more than the specified number of seconds to prevent client from infinite waiting for individual socket read operations due to dead connection. This can be used both as a force global query timeout and network problems detector. A value of zero (the default) turns this off.

or

Controls the number of seconds of connection inactivity to prevent client from infinite waiting for individual socket read operations due to dead connection. This can be used both as a force global query timeout and network problems detector. A value of zero (the default) turns this off.

Regards,
Kirk Jamison