From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
Cc: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: libpq should not look up all host addresses at once |
Date: | 2018-08-13 14:42:40 |
Message-ID: | 28510.1534171360@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> writes:
> In the same vein on a wrong password:
> sh> psql "host=no-such-host,local2.coelho.net,local3.coelho.net"
> Password for user fabien:
> psql: could not translate host name "no-such-host" to address: Name or service not known
> could not connect to server: Connection refused
> Is the server running on host "local2.coelho.net" (127.0.0.2) and accepting
> TCP/IP connections on port 5432?
> could not connect to server: Connection refused
> Is the server running on host "local2.coelho.net" (127.0.0.3) and accepting
> TCP/IP connections on port 5432?
> FATAL: password authentication failed for user "fabien"
> The Fatal error does not really say for which host/ip the password fail.
Yup, but that's not the province of this patch to improve. See
https://www.postgresql.org/message-id/25918.1533918960@sss.pgh.pa.us
for one that is trying to improve it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2018-08-13 14:45:07 | Re: Creating extensions for non-superusers |
Previous Message | Tom Lane | 2018-08-13 14:39:55 | Re: libpq should not look up all host addresses at once |