Andreas Karlsson <andr...@proxel.se> writes: > On 04/17/2016 09:28 PM, Bill Moran wrote: >> What I believe is happening, is that the pg connection libs >> first try to connect via ssl and get a password failed error, >> then fallback to trying to connect without ssl, and get a "no >> pg_hba.conf entry" error. The problem is that the second error >> masks the first one, hiding the real cause of the connection >> failure, and causing a lot of confusion.
> I got both the messages when I tried this with psql. What did you do > when you only got the second message? Maybe Bill tried it with a rather old libpq? This rings a bell as being something we fixed awhile back. regards, tom lane -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers