On 2005-05-02, Rob Butler <[EMAIL PROTECTED]> wrote: > Another option is to have the client driver send some > ignorable message instead of the server. If the > server doesn't get a message every timeout > minutes/seconds + slop factor, then it drops the > connection. So libpq, JDBC, .net etc would all have > to have this implemented, but the changes to the > server would probably be simpler this way, wouldn't they?
Then the client has to guarantee that it can stop whatever it was doing (which might have nothing to do with the database) every so often in order to send a message; this isn't feasible for most clients. The server-based method is actually no more complex to implement on the server end and does not impose any such restrictions on the client (even if the client sets the option and then ignores the database connection for a long time, all that happens is that the TCP window fills up). -- Andrew, Supernews http://www.supernews.com - individual and corporate NNTP services ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
