<p dir="ltr"><br /> On Apr 26, 2016 4:41 AM, "Tom Lane" <<a
href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>>wrote:<br /> ><br /> > Andreas Karlsson <<a
href="mailto:andreas@proxel.se">andreas@proxel.se</a>>writes:<br /> > > On 04/17/2016 09:28 PM, Bill Moran
wrote:<br/> > >> What I believe is happening, is that the pg connection libs<br /> > >> first try to
connectvia ssl and get a password failed error,<br /> > >> then fallback to trying to connect without ssl, and
geta "no<br /> > >> pg_hba.conf entry" error. The problem is that the second error<br /> > >> masks
thefirst one, hiding the real cause of the connection<br /> > >> failure, and causing a lot of confusion.<br
/>><br /> > > I got both the messages when I tried this with psql. What did you do<br /> > > when you
onlygot the second message?<br /> ><br /> > Maybe Bill tried it with a rather old libpq? This rings a bell<br />
>as being something we fixed awhile back.<br /> ><p dir="ltr">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.. <p dir="ltr">/Magnus