From: Tom Lane <tgl@sss.pgh.pa.us>
To: Fabien COELHO <coelho@cri.ensmp.fr>
cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Subject: Re: libpq should not look up all host addresses at once
In-reply-to: <alpine.DEB.2.21.1808111412560.29350@lancre>
References: <4913.1533827102@sss.pgh.pa.us>
 <alpine.DEB.2.21.1808111122220.1705@lancre>
 <alpine.DEB.2.21.1808111412560.29350@lancre>
Comments: In-reply-to Fabien COELHO <coelho@cri.ensmp.fr>
	message dated "Sat, 11 Aug 2018 14:15:44 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <28509.1534171360.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 13 Aug 2018 10:42:40 -0400
Message-ID: <28510.1534171360@sss.pgh.pa.us>
Precedence: bulk

Fabien COELHO <coelho@cri.ensmp.fr> writes:
> In the same vein on a wrong password:

>   sh> psql "host=3Dno-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) a=
nd 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) a=
nd 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