Sorry this is an extremely old thread, but I finally got around to
tracking down the problem.. Added these lines to postgres.conf and
poof, problem gone..
tcp_keepalives_idle = 60 # TCP_KEEPIDLE, in seconds;
tcp_keepalives_interval = 10 # TCP_KEEPINTVL, in seconds;
tcp_keepalives_count = 5 # TCP_KEEPCNT;
Hope this helps someone else!
On Sat, Oct 30, 2010 at 4:21 AM, Mike Christensen <mike@kitchenpc.com> wrote:
> Maybe that's it.. It's definitely some sort of SSL thing since it
> didn't start happening until I enabled SSL. I guess I'll just have to
> close pgAdmin when I'm not using it..
>
> On Sat, Oct 30, 2010 at 12:57 AM, Basil Bourque <basil.list@me.com> wrote:
>>
>> On Oct 29, 2010, at 15:36, Mike Christensen wrote:
>>
>>> I have a Postgres 9 server running on a server out on the Internet and
>>> I connect to it with pgAdmin on OS/X over an SSL connection.
>>>
>>> I notice if I keep the connection open and idle for maybe an hour or
>>> so, when I try to run a query it either times out or pgAdmin just
>>> kinda freezes up and I have to force quit.. Is there some sort of
>>> idle timeout setting on SSL connections, or maybe it has to
>>> re-negotiate the connection after a certain amount of idle time and
>>> it's not doing that right?
>>>
>>> Anyone run into this before? Thanks!
>>
>> I don't know about pgAdmin or SSL, but I have heard that routers and switches
>> can have a timeout limit: "the idle time after which an established
>> connection of any protocol closes".
>>
>> http://search.gmane.org/?query=router+timeout&group=gmane.comp.lang.inug-4d.tech
>>
>> --Basil Bourque
>>
>>
>>
>> --
>> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-general
>>
>
