On Fri, Jun 9, 2017 at 3:22 PM, Heikki Linnakangas <hlinn...@iki.fi> wrote:
> Hmm, there is one problem with our current use of comma as a separator:
> 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
[2] Fix for comma in UDS path

Reply via email to