| 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:57:16 |
| Message-ID: | CA+OCxowvn0j8ti_tO03rEEU5S84+EVv=38MHa9VQ=2=wzgB5sw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
On Fri, Dec 19, 2014 at 3:37 PM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> On 12/19/2014 11:24 PM, Dave Page wrote:
>> That's what does happen.
>
> Oh, I see, but the password matching for caching doesn't work.
>
> IIRC pgadmin creates a pgpass file, right? So to do this for ssh tunnels
> you'd have to dynamically add entries (ugly) or change use of .pgpass to
> instead use a callback within pgadmin .
Right - we'd have to store the entries somewhere based on the target
server and the SSH config, and dynamically rebuilt the pgpass file
during the connection process. That seems a) ugly and b) very fragile.
--
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 16:02:27 | Re: Massively annoying bug still not fixed in v1.20 :-( |
| Previous Message | Craig Ringer | 2014-12-19 15:37:25 | Re: Massively annoying bug still not fixed in v1.20 :-( |