On Apr 26, 2016 4:41 AM, "Tom Lane" <t...@sss.pgh.pa.us> wrote: > > 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. >
Yeah, libpq used to keep just one error message. Iirc, this was changed quite long ago though, but I guess if it's a really old libpq.. /Magnus