On Mon, January 14, 2008 12:49 pm, henry wrote:
> WRT the origional question: why is tcp_keepalives_idle being ignored
> (whether with SET or in postgresql.conf)? - ie, SHOW ALL says it's 0 no
> matter what I do.
A quick follow-on with more info to my own post.
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.
Regards
Henry
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
