RE: Timeout parameters - Mailing list pgsql-hackers

From Tsunakawa, Takayuki
Subject RE: Timeout parameters
Date
Msg-id 0A3221C70F24FB45833433255569204D1FB9F574@G01JPEXMBYT05
Whole thread Raw
In response to RE: Timeout parameters  ("Jamison, Kirk" <k.jamison@jp.fujitsu.com>)
Responses RE: Timeout parameters
List 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
notterminate 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



pgsql-hackers by date:

Previous
From: "Jamison, Kirk"
Date:
Subject: RE: libpq debug log
Next
From: "Tsunakawa, Takayuki"
Date:
Subject: RE: reloption to prevent VACUUM from truncating empty pages at theend of relation