From: | Ian Zimmerman <nobrowser(at)gmail(dot)com> |
---|---|
To: | pgadmin-support(at)lists(dot)postgresql(dot)org |
Subject: | postgres tunnelling article |
Date: | 2022-01-12 05:07:34 |
Message-ID: | CAP9AG=Dk9BJV4DjF=qQPtjHL9EkVd3Hk9jSCB4s8Oxu2xm53sg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
I have just read your post:
https://www.enterprisedb.com/blog/ssh-tunneling-pgadmin-4
The latest versions of OpenSSH provide tunnelling to local sockets: you can
have something like
this in your .ssh/config:
Host myserver
LocalForward 9000 /run/supervisor.sock
or the equivalent command line syntax:
ssh -L 9000:/run/supervisor.sock myserver
I have tried to make use of this with pgAdmin, but unsuccessfully: it
insists that the remote end looks like a hostname and a port. It's a shame
because authentication on the postgres local socket is completely painless,
it just uses my uid, but connecting to the TCP port requires a password and
blah blah. Do you know if there are plans to add this very convenient
feature to pgAdmin?
Ian
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2022-01-12 10:12:57 | Re: SQL query that can be used to generate the same output shown in the SQL tab within pgadmin? |
Previous Message | Ni Ne | 2022-01-12 00:44:50 | SQL query that can be used to generate the same output shown in the SQL tab within pgadmin? |