Re: tcp_keepalives_idle ignored
От | henry |
---|---|
Тема | Re: tcp_keepalives_idle ignored |
Дата | |
Msg-id | 63000.196.23.181.69.1200314387.squirrel@zenmail.co.za обсуждение исходный текст |
Ответ на | Re: tcp_keepalives_idle ignored ("henry" <henry@zen.co.za>) |
Ответы |
Re: tcp_keepalives_idle ignored
|
Список | pgsql-general |
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
В списке pgsql-general по дате отправления: