Eduardo Piombino <drakorg@xxxxxxxxx> wrote: > (the timer had stopped almost exactly at 2 hours, 7.210.123 ms to > be exact, which makes me think of a 2 hours timeout somewhere). The most likely cause of this would be that you were accessing the server through a firewall with neither the client nor the server configured for TCP keepalive messages, or configured to an initial delay longer than the firewall is willing to tolerate. The default for initial delay in most environments is two hours, with a few retries at much shorter intervals after that. Or it could be that the client was using TCP keepalive, and the network was down when it hit the two hour mark and tried to confirm that the connection was still good. http://www.postgresql.org/docs/current/static/runtime-config-connection.html http://www.postgresql.org/docs/current/static/libpq-connect.html http://tldp.org/HOWTO/TCP-Keepalive-HOWTO/overview.html http://superuser.com/questions/729034/any-way-to-keep-connection-alive-in-pgadmin-without-setting-it-on-the-server -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
