| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | hushthatbush(at)hushmail(dot)com, "pgadmin-support(at)postgresql(dot)org" <pgadmin-support(at)postgresql(dot)org> |
| Subject: | Re: Massively annoying bug still not fixed in v1.20 :-( |
| Date: | 2014-12-19 15:24:48 |
| Message-ID: | CA+OCxoyL0QPmMCsB4p=XKgRu8dKGgQ1RMdT0uCkEDsCoZJdRRg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
On Fri, Dec 19, 2014 at 3:11 PM, Craig Ringer <craig(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2014-12-19 15:37:25 | Re: Massively annoying bug still not fixed in v1.20 :-( |
| Previous Message | Craig Ringer | 2014-12-19 15:11:03 | Re: Massively annoying bug still not fixed in v1.20 :-( |