On Fri, Dec 19, 2014 at 3:37 PM, Craig Ringer <cr...@2ndquadrant.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 -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
