On Sun, 1 May 2005, Alvaro Herrera wrote:
> Well, if process A loses the connection to the client, then the
> transaction will be rolled back and other processes will be able to
> continue.
If the other end of a tcp/ip connection just disapears, for example if the
network cable is cut off then in linux it can take up to 2 hours as
default for it to close the connection. Normally if a client application
dies then the client OS cleans up and closes the socket so that the server
knows about it.
There are some settings that one can alter to change the time it waits
before probing and killing the connection, ie tcp_keepalive_time in
/proc/sys/net/ipv4/.
It's documented in "man tcp" that say that it will take 2h11m as default
to kill of such a connection.
Pg could of course also implement some pinging protocl that should be done
every now and then by the client so that the server knows that it is
alive. For now you just have to lower the global settings as the one above
if you want it to handle it better.
--
/Dennis Björklund
---------------------------(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
