From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Rob Sargent <robjsargent(at)gmail(dot)com> |
Cc: | pgsql-jdbc(at)lists(dot)postgresql(dot)org |
Subject: | Re: Overly specific error message? |
Date: | 2019-06-01 17:07:13 |
Message-ID: | CADK3HHJYCUBOv5QkMAgExLfCq6_97mQq5xHQ6uJgae5VOjX2tQ@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Thu, 30 May 2019 at 18:16, Rob Sargent <robjsargent(at)gmail(dot)com> wrote:
> Using PG 10.7 and JDBC org.postgresql:postgresql:42.1.4
>
> I had only a single slash between postgresql: and the host
>
> jdbc:postgresql:/some.host.name:5432
>
> I got
>
> org.postgresql.util.PSQLException: FATAL: password authentication failed
> for user "some-name"
>
> Naturally I tested and re-tested connecting manually as that user and with
> the supplied password. Eventually of course I started looking around a
> little more thoroughly...
>
> I wonder if the message needs to be specifically about password
> authentication?
>
Interesting.
My guess it it parsed the URL and did *something* and presented it to the
server
Off the top of my head parsing should be fixed
Dave Cramer
davec(at)postgresintl(dot)com
www.postgresintl.com
From | Date | Subject | |
---|---|---|---|
Next Message | maltalex | 2019-06-06 12:29:49 | [pgjdbc/pgjdbc] 1970c4: Make LogSequenceNumber implement Comparable<LogSeq... |
Previous Message | Rob Sargent | 2019-05-30 22:15:53 | Overly specific error message? |