Re: Unable to connect to 9.5 via JDBC driver 1207
От | Thomas Kellerer |
---|---|
Тема | Re: Unable to connect to 9.5 via JDBC driver 1207 |
Дата | |
Msg-id | n8r2gg$hln$1@ger.gmane.org обсуждение исходный текст |
Ответ на | Re: Unable to connect to 9.5 via JDBC driver 1207 (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Unable to connect to 9.5 via JDBC driver 1207
Re: Unable to connect to 9.5 via JDBC driver 1207 |
Список | pgsql-jdbc |
Tom Lane schrieb am 02.02.2016 um 20:38: >>> As I said: by simply switching to the previous driver, everything was fine. >>> It works fine with JDBC connections to localhost, but not to a remote >>> server (psql was fine) >>> I had also one user of SQL Workbench/J who reported the same problem and >>> after switching to 1206 the problem went away for him as well. > >> Well clearly we would like to get to the root of this problem. Is it >> possible for you to provide us with more information? > > Since the quoted error message mentions a connection from "127.0.0.1", > it's impossible that it is a reply from a remote server (unless your > networking configuration is completely broken). Presumably what is > happening is that what you think is a connection to a remote PG server > is actually being made to localhost, and the local PG server's pg_hba.conf > doesn't allow the username and/or dbname. You could check that by turning > on log_connections on both servers. > > As to why that would happen as a consequence of a driver version change, > I'm pretty clueless, but I would wonder about differences in driver config > files or the driver's interpretation of a connection URL. In any case, > certainly not enough information has been given to diagnose it. The initial error message in this thread was not from me. I am currently not in the office, but I will see if I can reproduce that tomorrow. I have also contacted the SQL Workbench/J user who reported this to me last week and asked him to describe his setup as well. In his case, the error message was: > FATAL: no pg_hba.conf entry for host "213.xxx.xx.xxx", user "foobar", database "postgres", SSL on If I understood him correctly, he has no access to the server, so the only thing he did, was to change the driver and he could connect again. Thomas
В списке pgsql-jdbc по дате отправления: