From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
---|---|
To: | Eduardo Piombino <drakorg(at)gmail(dot)com>, PGSQL Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Disconnected but query still running |
Date: | 2015-07-14 21:12:31 |
Message-ID: | 2140079031.2200934.1436908351169.JavaMail.yahoo@mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Eduardo Piombino <drakorg(at)gmail(dot)com> 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
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2015-07-14 22:39:52 | Re: Creating table with data from a join |
Previous Message | William Dunn | 2015-07-14 20:11:54 | Re: Index Only Scan vs Cache |