I run a VPN. I did not see this problem with PgAdmin (1.14).
I connected to the VPN, then I started PgAdmin and ran a query.
Then I disconnected the VPN and ran the query again. No problem.
Then I reconnected the VPN and ran the query once again. No problem.
I also tested it started PgAdmin first, then starting the VPN.
No combination of connects/disconnects produced any problem with PgAdmin.
I am running Windows 7
On Thu, Jun 30, 2011 at 3:12 AM, Guillaume Lelarge
> 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
> Sent via pgadmin-support mailing list (pgadmin-support(at)postgresql(dot)org)
> To make changes to your subscription:
In response to
pgadmin-support by date
|Next:||From: Ronney M. de Castro||Date: 2011-06-30 13:08:33|
|Subject: Help in postgre Charset|
|Previous:||From: Dave Page||Date: 2011-06-30 08:34:23|
|Subject: Re: pgadmin and broken connections|