Re: libpq host/hostaddr/conninfo inconsistencies

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: libpq host/hostaddr/conninfo inconsistencies
Date: 2019-02-14 21:51:40
Message-ID: alpine.DEB.2.21.1902142224380.20189@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
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= hostaddr=") 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.


In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2019-02-14 22:17:47 Re: Ryu floating point output patch
Previous Message Tom Lane 2019-02-14 21:45:38 Re: Using POPCNT and other advanced bit manipulation instructions