On Dec 19, 2014 5:02 PM, "Craig Ringer" wrote:
>
> On 12/19/2014 11:57 PM, Dave Page wrote:
> > 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) v
On Fri, Dec 19, 2014 at 4:02 PM, Craig Ringer wrote:
> On 12/19/2014 11:57 PM, Dave Page wrote:
>> 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)
On 12/19/2014 11:57 PM, Dave Page wrote:
> 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.
Darn. I thought libpq had a callback for a p
On Fri, Dec 19, 2014 at 3:37 PM, Craig Ringer 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 ad
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 callba
On Fri, Dec 19, 2014 at 3:11 PM, Craig Ringer 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 agai
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
On Fri, Dec 19, 2014 at 1:45 PM, wrote:
> I always connect to PostgreSQL over an SSH tunnel. As such, I have no need
> for a special password for the PostgreSQL server, as it's already over a SSH
> tunnel. I assume this is how 99% of all users do things.
>
> Why, then, does it need to ask me ever
I always connect to PostgreSQL over an SSH tunnel. As such, I have no
need for a special password for the PostgreSQL server, as it's already
over a SSH tunnel. I assume this is how 99% of all users do things.
Why, then, does it need to ask me every single time for a password,
even though I have ch
I'm pleased to announce that pgAdmin 1.20.0 is now available for
download in source code form, and for Windows and Mac from:
http://www.pgadmin.org/download/index.php
It is also included in the PostgreSQL 9.4 Installers from EDB.
This new release include various new features and bug fixes, as we
10 matches
Mail list logo
