Re: Massively annoying bug still not fixed in v1.20 :-(

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Dave Page <dpage(at)pgadmin(dot)org>, hushthatbush(at)hushmail(dot)com
Cc: "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:11:03
Message-ID: 54944007.5030203@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

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.

You can do this with a libpq connection callback.

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Dave Page 2014-12-19 15:24:48 Re: Massively annoying bug still not fixed in v1.20 :-(
Previous Message Dave Page 2014-12-19 13:51:14 Re: Massively annoying bug still not fixed in v1.20 :-(