Re: "unix_socket_directories" should be GUC_LIST_INPUT? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: "unix_socket_directories" should be GUC_LIST_INPUT?
Date
Msg-id 1059330.1603815802@sss.pgh.pa.us
Whole thread Raw
In response to Re: "unix_socket_directories" should be GUC_LIST_INPUT?  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: "unix_socket_directories" should be GUC_LIST_INPUT?
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> If we change this, is it going to be a compatibility break for the
> contents of postgresql.conf files?

I think not, at least not for the sorts of values you'd ordinarily
find in that variable, say '/tmp, /var/run/postgresql'.  Possibly
the behavior would change for pathnames containing spaces or the
like, but it is probably kinda broken for such cases today anyway.

In any case, Michael had promised to test this aspect before committing.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: "unix_socket_directories" should be GUC_LIST_INPUT?
Next
From: Paul Jungwirth
Date:
Subject: Re: SQL:2011 PERIODS vs Postgres Ranges?