From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bill Moran <wmoran(at)potentialtech(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Andreas Karlsson <andreas(at)proxel(dot)se> |
Subject: | Re: Can we improve this error message? |
Date: | 2016-04-26 07:00:55 |
Message-ID: | CABUevEw1m6=FBq+ywbKhB+_x4aroVvzPmCzJmdAJRhnErfq+4Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Apr 26, 2016 4:41 AM, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Andreas Karlsson <andreas(at)proxel(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Gustafsson | 2016-04-26 08:34:01 | Typo in execProcnode.c documentation |
Previous Message | Noah Misch | 2016-04-26 06:38:22 | Re: pg_dump dump catalog ACLs |