Dave,
>> I think I can reproduce the above pattern 100% of the time. Note that
>> pgadmin stays up until I make the mistake of clicking on the object browser.
>
> For the benefit of the list, I just re-wrote much of the code that
> handles this, and posted a proposed patch to the hackers list:
>
On Tue, Jul 12, 2011 at 5:45 PM, Josh Berkus wrote:
>
>>> Booo. I spoke too soon. While reconnecting the query window works
>>> perfectly, reconnecting the object navigator does not. I just get
>>> "refreshing server __ ... failed".
>>
>> I'm unable to recreate that :-(
>
> Well, it's happ
>> Booo. I spoke too soon. While reconnecting the query window works
>> perfectly, reconnecting the object navigator does not. I just get
>> "refreshing server __ ... failed".
>
> I'm unable to recreate that :-(
Well, it's happening pretty consistently here:
1) create an SSH tunnel to a
On Mon, Jul 11, 2011 at 10:18 PM, Josh Berkus wrote:
> On 7/11/11 12:09 PM, Josh Berkus wrote:
>> Dave, Guillaume,
>>
>> I've tested 1.14b2 on OSX 10.5 and reconnecting now works perfectly. It
>> even worked after I put the laptop to sleep and changed networks and
>> then reconnected the VPN.
>
>
On 7/11/11 12:09 PM, Josh Berkus wrote:
> Dave, Guillaume,
>
> I've tested 1.14b2 on OSX 10.5 and reconnecting now works perfectly. It
> even worked after I put the laptop to sleep and changed networks and
> then reconnected the VPN.
Booo. I spoke too soon. While reconnecting the query window
Dave, Guillaume,
I've tested 1.14b2 on OSX 10.5 and reconnecting now works perfectly. It
even worked after I put the laptop to sleep and changed networks and
then reconnected the VPN.
Yy!
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgadmin-support mailing list
On Fri, 2011-07-01 at 13:50 +0200, Christophe Chauvet wrote:
> Hi Guillaume
>
> I have this issue but not only with VPN. You can reproduce by using
> SSH with -L argument as
>
> ssh -L 2000:127.0.0.1:5432 myuser@my_ip
>
> launch PgAdmin with localhost avec IP and port 2000
>
> execute a query,
Hi Guillaume
I have this issue but not only with VPN. You can reproduce by using
SSH with -L argument as
ssh -L 2000:127.0.0.1:5432 myuser@my_ip
launch PgAdmin with localhost avec IP and port 2000
execute a query, go to you terminal, press Ctrl + C to cut the
connection and retry the previous c
On Thu, Jun 30, 2011 at 7:31 PM, Josh Berkus wrote:
> On 6/30/11 9:49 AM, Josh Berkus wrote:
>>
>>> 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?
>>
>> 1.12. Let me try upgrading, and I'll report back.
On 6/30/11 9:49 AM, Josh Berkus wrote:
>
>> 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?
>
> 1.12. Let me try upgrading, and I'll report back.
Well, I can't tell you because I can't seem to use 1.14b1
> 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?
1.12. Let me try upgrading, and I'll report back.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgadmin-support mailing list
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,
On Thu, Jun 30, 2011 at 9:12 AM, Guillaume Lelarge
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
>>
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
On 6/29/11 1:10 PM, Josh Berkus wrote:
> all. If my connection was over a VPN, and the VPN, and I log back in,
"... and the VPN kicks me off ... "
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make cha
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 ex
16 matches
Mail list logo