From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: libpq host/hostaddr/conninfo inconsistencies |
Date: | 2019-02-21 15:33:36 |
Message-ID: | 21393.1550763216@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:
>> My only complaint about this is that it makes it sound like you *must*
>> provide "host", even when giving "hostaddr":
> That is the idea, "hostaddr" is moslty never needed.
Sure, you only need it if you want to bypass DNS lookup, but if you
do that, you don't necessarily need to give "host" as well. Changing
the documentation to imply that you do would not be an improvement.
> It is the initial misleading issue I've been complaining about: one can
> specify an IP *both* in host (although it is not documented) and in
> hostaddr... and when both are provided, things started being messy
Indeed, but the verbiage being suggested here actually encourages
people to do that, by falsely implying that they have to supply
both parameters.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Kuntal Ghosh | 2019-02-21 15:37:52 | Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits |
Previous Message | Andreas Karlsson | 2019-02-21 15:27:06 | Re: Journal based VACUUM FULL |