| From: | Tim Uckun <timuckun(at)gmail(dot)com> |
|---|---|
| To: | pgadmin-support(at)postgresql(dot)org |
| Subject: | Re: Pgadmin III loses connection with remote database and then hangs for a long time. |
| Date: | 2011-06-01 22:08:09 |
| Message-ID: | BANLkTi==nrrZ-Hy79GRzuV=xdxtBdEbQfw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
>
> The default TCP connection timeout is around 3 1/2 minutes. This is left
> over from the leased line and slow connection days when the protocol was
> defined and has never been updated to match the reality of high speed
> networks. This may be the timer it is waiting for. Some of the
> MS-Windows network drivers in particular are notorious for locking up
> the workstation while waiting for events that never happen. Losing a
> remote shared drive you have mapped into often causes very similar
> symptoms. But I am not one to speculate about the internals when I have
> never looked at the code. I find it much better to report the symptoms
> with as much supporting data as I can so the people that understand how
> it works can do the diagnosis.
I didn't mean to imply I had a definitive answer. That's just how it
looks like to me. BTW I am on linux.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kieran McCusker | 2011-06-02 09:46:34 | Re: Performance of pgAdmin 14 Beta 1 |
| Previous Message | Guillaume Lelarge | 2011-06-01 20:31:39 | Re: pg_listener table errors with slony |