Re: tcp_keepalives_idle ignored

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "henry" <henry(at)zen(dot)co(dot)za>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: tcp_keepalives_idle ignored
Date: 2008-01-14 15:46:07
Message-ID: 14312.1200325567@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"henry" <henry(at)zen(dot)co(dot)za> writes:
> The culprit in my case was a local trigger firing on INSERTs using
> dblink_exec() without 'host=127.0.0.1'. Bad news though, even _with_
> 'host=127.0.0.1' the connections do not idle timeout. They just hang
> around waiting for the rapture.

> So,... this appears to be dblink related after all. I'll be trying
> explicit open/exec/close. Weird that dblink_exec in a trigger doesn't
> release resources.

Hmm, this is the transient-connection form of dblink? If so, that would
be a bug. Can you put together a test case? Also, which PG version are
you using, exactly?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-01-14 15:57:45 Re: ECPG problem with 8.3
Previous Message Tom Lane 2008-01-14 15:44:12 Re: tcp_keepalives_idle ignored