| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgadmin-support(at)postgresql(dot)org |
| Subject: | Re: pgadmin and broken connections |
| Date: | 2011-06-30 08:34:23 |
| Message-ID: | BANLkTi=BQKO+bjQ=G365XzKCvUE2_G2UMg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
On Thu, Jun 30, 2011 at 9:12 AM, Guillaume Lelarge
<guillaume(at)lelarge(dot)info> wrote:
> On Wed, 2011-06-29 at 13:10 -0700, Josh Berkus wrote:
>> All,
>>
>> I'm not sure if anyone uses pgadmin over as many VPNs as I do, and has
>> noticed this.
>>
>> On OSX, at least, pgadmin can't deal with broken database connections at
>> all. If my connection was over a VPN, and the VPN, and I log back in,
>> there is no way to get pgadmin to reconnect to that database except by
>> shutting down pgadmin completely and restarting it.
>>
>> Is this an issue which is common to all platforms? Or an OSX-specific
>> issue?
>>
>
> We had some previous reports about this. The issue is that I can't
> reproduce it (mainly because I don't have a PostgreSQL server on a VPN
> connection).
Also there seems to be some confusion over the versions of pgAdmin
affected. 1.14 has improvements over 1.12 - which are you using Josh?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Shapiro | 2011-06-30 08:56:37 | Re: pgadmin and broken connections |
| Previous Message | Guillaume Lelarge | 2011-06-30 08:12:50 | Re: pgadmin and broken connections |