Re: Massively annoying bug still not fixed in v1.20 :-( - Mailing list pgadmin-support

From Dave Page
Subject Re: Massively annoying bug still not fixed in v1.20 :-(
Date
Msg-id CA+OCxoyL0QPmMCsB4p=XKgRu8dKGgQ1RMdT0uCkEDsCoZJdRRg@mail.gmail.com
Whole thread Raw
In response to Re: Massively annoying bug still not fixed in v1.20 :-(  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: Massively annoying bug still not fixed in v1.20 :-(
List pgadmin-support
On Fri, Dec 19, 2014 at 3:11 PM, Craig Ringer <craig@2ndquadrant.com> wrote:
> On 12/19/2014 09:51 PM, Dave Page wrote:
>> It's not going to work because when using an SSH tunnel we have to use
>> a random port number for the client end of the tunnel. When libpq (not
>> pgAdmin) tries to match the connection details against those that are
>> stored, it will often fail because the port number won't match.
>
> Why not handle it like libpq does?
>
> Connect, and if the server asks for a password *then* prompt the user.

That's what does happen.

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

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



pgadmin-support by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Massively annoying bug still not fixed in v1.20 :-(
Next
From: Craig Ringer
Date:
Subject: Re: Massively annoying bug still not fixed in v1.20 :-(