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

From Robert Haas
Subject Re: "unix_socket_directories" should be GUC_LIST_INPUT?
Date
Msg-id CA+TgmoYZuc-UNnxqwOVK2hXhMnujsCesk32ExhYnE6y91X=_PA@mail.gmail.com
Whole thread Raw
In response to Re: "unix_socket_directories" should be GUC_LIST_INPUT?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: "unix_socket_directories" should be GUC_LIST_INPUT?
List pgsql-hackers
On Tue, Oct 27, 2020 at 9:45 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> > If we're going to change it I think we need an updated patch that covers
> > pg_dump.  (Even if we argue that pg_dump would not normally dump this
> > variable, keeping it up to date with respect to GUC_LIST_QUOTE seems
> > proper.)
>
> Right, I was definitely assuming that that would happen.

If we change this, is it going to be a compatibility break for the
contents of postgresql.conf files?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Adam Brusselback
Date:
Subject: Re: Implementing Incremental View Maintenance
Next
From: Tom Lane
Date:
Subject: Re: "unix_socket_directories" should be GUC_LIST_INPUT?