Re: libpq host/hostaddr/conninfo inconsistencies
Fabien COELHO <coelho@cri.ensmp.fr>
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Andres Freund <andres@anarazel.de>
Cc: Robert Haas <robertmhaas@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-02-14T21:51:40Z
Lists: pgsql-hackers
> On 2018-10-26 09:21:51 +0200, Fabien COELHO wrote: >> (1) you are somehow against changing the current implementation, eg erroring >> out on possibly misleading configurations, because you do not think it is >> really useful to help users in those cases. > > I find this formulation somewhat passive aggressive. I do not understand what you mean by that expression. I was just trying to sum-up Robert's opposition to erroring on misleading configurations (eg "host=1.2.3.4 hostaddr=4.3.2.1") instead of complying to it whatever, as is currently done. Probably my phrasing could be improved, but I do not think that I misrepresented Robert's position. Note that the issue is somehow mitigated by 6e5f8d489a: \conninfo now displays a more precise information, so that at least you are not told that you are connected to a socket when you a really connected to an ip, or to one ip when you a really connected to another. -- Fabien.
Commits
-
libpq docs: be clearer about conninfo's 'hostaddr'
- 75f46eaee20c 13.0 landed
-
psql: Show IP address in \conninfo
- 6e5f8d489acc 12.0 landed