From: | Derrick Rice <derrick(dot)rice(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | What could keep a connection / query alive? |
Date: | 2011-03-28 16:02:16 |
Message-ID: | AANLkTinTECxxV9t0RY_Ubb9d2yc6huYTdW7OGpFA=eX2@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi folks,
I'm investigating (using 8.2) an instance of a database client connection
remaining open in a single query well past statement timeout settings. I
understand that severed TCP connections can cause the backend to hang until
the connection is closed, but our tcp keepalive settings should have
recognized that condition after about 30 minutes. The connection and
backend didn't terminate for nearly 90 minutes.
What can cause this? Why would these tcp and statement timeout settings not
terminate the backend?
Active Query Time (from pg_stat_activity): 01:27:44 - 00 days
Statement Timeout: 2 minutes
tcp_keepalives_idle=20min
(count and interval set to 0, using system defaults)
system keepalive settings are default for Linux, being:
count: 9
interval: 75
Expect severed connections to be detected within 20 min + 9*75s < 32min.
Thanks,
Derrick
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Crawford | 2011-03-28 16:12:47 | Re: A simpler time zone question |
Previous Message | Tom Lane | 2011-03-28 15:57:43 | Re: A simpler time zone question |