Robert Haas <robertmhaas@gmail.com> writes:
> Maybe:
> listen_addresses = { host | host:port | * | *:port } [, ...]
> unix_socket_directory = { directory | directory:port ] [,...]
> ...except that colon is a valid character in a directory name. Not
> sure what to do about that.
Do we need to do anything? There are no standard scenarios in which a
colon would appear in such paths, and I don't see why we need to cater
for it. (Remember that Windows doesn't enter into this ...)
regards, tom lane
