I believe the main problem in this situation is that you are trying to use a security context that only exists on the server you are trying to connect to, this is not available from a remote client.
You need to setup a authentication method that does allow this, or specify credentials on connecting HTH Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl Convince Microsoft! They need to add TRUNCATE PARTITION in SQL Server https://connect.microsoft.com/SQLServer/feedback/details/417926/truncate-partition-of-partitioned-table 2013/1/13 Adrian Klaver <adrian.kla...@gmail.com> > On 01/12/2013 04:29 PM, Paul S wrote: > >> Thanks Adrian, >> > > I think I can work with that but it's just a little less optimal that I >> was >> hoping for. Logging in just like I do in SSH would have been much easier. >> > > Just had a thought. Could you not set up SSH keys for the postgres user > and connect the tunnel as that user directly? > > >> Thanks, >> >> Paul >> >> >> >> >> >> > > > -- > Adrian Klaver > adrian.kla...@gmail.com > > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/**mailpref/pgsql-general<http://www.postgresql.org/mailpref/pgsql-general> >
