Skip site navigation (1) Skip section navigation (2)

Re: Handling connection loss

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>
Subject: Re: Handling connection loss
Date: 2011-07-19 08:53:35
Message-ID: CA+OCxoyrH5X3=AQ0v0Y_c6_EQRWd93k_HD0a6nYm3bQ_H5TXwQ@mail.gmail.com (view raw or flat)
Thread:
Lists: pgadmin-hackers
On Mon, Jul 18, 2011 at 9:11 PM, Guillaume Lelarge
<guillaume(at)lelarge(dot)info> wrote:
>
> Did some tests and found something weird. I connect pgadmin to a
> database, I look into some objects with pgAdmin's browser. Then, I stop
> PostgreSQL, and start it again. Next object I click on will display a
> nice "lost connection" message, and another messagebox asking me if I
> want to reconnect. I click Yes and everything seems good (iow, I have
> the info I asked). I then click on another object, and it asks me again
> if I want to reconnect. Weird. I click Yes, and I get reconnected, and I
> won't be bothered again. I find it weird to have to say Yes two times
> when the connection was lost only once.

Was the second object in the same database? Don't forget that we might
have to restore multiple connections to individual databases, and the
maintenance DB - and we only test them when we need them.

> Moreover, with the SSH tunnel as described by Christophe Chauvet on
> -support, I don't even have the message box asking me if I want to
> reconnect.

I was testing using Josh's SSH tunnel test primarily, so that worked
well for me. Can you describe the steps to reproduce the issue?



-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

pgadmin-hackers by date

Next:From: Dave PageDate: 2011-07-19 09:01:41
Subject: Re: Handling connection loss
Previous:From: Dave PageDate: 2011-07-19 08:47:06
Subject: Re: Website

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group