RE: Timeout parameters
Tsunakawa, Takayuki <tsunakawa.takay@jp.fujitsu.com>
From: "Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>
To: "Jamison, Kirk" <k.jamison@jp.fujitsu.com>, "Nagaura, Ryohei" <nagaura.ryohei@jp.fujitsu.com>
Cc: 'Michael Paquier' <michael@paquier.xyz>, "AYahorau@ibagroup.eu" <AYahorau@ibagroup.eu>, 'Fabien COELHO' <coelho@cri.ensmp.fr>, "'pgsql-hackers@postgresql.org'" <pgsql-hackers@postgresql.org>, "MikalaiKeida@ibagroup.eu" <MikalaiKeida@ibagroup.eu>
Date: 2019-02-22T01:59:20Z
Lists: pgsql-hackers
From: Jamison, Kirk [mailto:k.jamison@jp.fujitsu.com] > socket_timeout (integer) libpq documentation does not write the data type on the parameter name line. > 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. The second one is better, but: * Just "connection inactivity" (i.e. the application hasn't submitted any request to the server for a long time) does not terminate the connection. * "due to dead connction" is not the cause for the timeout. If the timeout occurs, consider the connection dead (see keepalives_count). * Not restricted to "read" operation? Regards Takayuki Tsunakawa
Commits
-
Add support TCP user timeout in libpq and the backend server
- 249d64999615 12.0 landed