| From: | Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: List of hostaddrs not supported |
| Date: | 2017-06-09 10:22:20 |
| Message-ID: | CAD__OujJmjd35cCgaoMoQBdYS1OGJ+qA2vDJcP8PBrTd3Pi6eA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 9, 2017 at 3:22 PM, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> Hmm, there is one problem with our current use of comma as a separator:
you
> cannot use a Unix-domain socket directory that has a comma in the name,
> because it's interpreted as multiple hostnames. E.g. this doesn't work:
>
> psql "host=/tmp/dir,with,commas"
>
> For hostnames, ports, and network addresses (hostaddr), a comma is not a
> problem, as it's not a valid character in any of those.
>
> I don't know if that was considered when this patch was developed. I
> couldn't find a mention of this in the archives. But in any case, that's
> quite orthogonal to the rest of this thread.
I think this was found earlier [1]. But It appeared difficult to fix
without breaking other API's behavior [2]
[1] UDS with comma in name
<https://www.postgresql.org/message-id/CAD__OujtKhMV9kQhQ2sgWV9EyzSv_Gwd7Kd%3DP1Lq%2B0z8xhW1RQ%40mail.gmail.com>
[2] Fix for comma in UDS path
<https://www.postgresql.org/message-id/CAD__Ouj-13zkmkm6CX7dW3UE%2BOaAHvaOB9Yx-bYj4yOHmsJ_FQ%40mail.gmail.com>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2017-06-09 10:36:07 | Re: List of hostaddrs not supported |
| Previous Message | Heikki Linnakangas | 2017-06-09 10:06:57 | pgsql: Give a better error message on invalid hostaddr option. |