From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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-11 12:15:44 |
Message-ID: | alpine.DEB.2.21.1808111412560.29350@lancre |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> * when the password is required, there is no way to know for which host/ip it
> is:
>
> sh> psql "host=127.0.0.17,local2.coelho.net,local.coelho.net"
> Password for user fabien:
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.
Basically, with multiple hostnames and ips per hostname, error messages
need to be more precise.
--
Fabien.
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2018-08-11 13:11:19 | Re: logical decoding / rewrite map vs. maxAllocatedDescs |
Previous Message | Fabien COELHO | 2018-08-11 10:18:48 | Re: libpq should not look up all host addresses at once |