| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, 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:57:32 |
| Message-ID: | 22313.1550764652@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> From my point of view, the issue here is that the way the
> documentation is written right now tends to lead people to believe
> that if they have a host name, they must pass it via host, and if they
> have an IP address, they must pass it via hostaddr. Thus pgAdmin 3,
> at least, had code to check whether the input looked like an IP
> address and put it into one field or the other accordingly. And
> that's stupid.
True, but isn't that because we fail to document at all that you
can put an IP address in "host"? Which your proposed patch didn't
change, IIRC.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2019-02-21 16:04:43 | Re: libpq host/hostaddr/conninfo inconsistencies |
| Previous Message | Tom Lane | 2019-02-21 15:55:39 | Re: libpq host/hostaddr/conninfo inconsistencies |