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

From Peter Eisentraut
Subject Re: "unix_socket_directories" should be GUC_LIST_INPUT?
Date
Msg-id 414434e5-a16d-6c82-131a-d155f400c2ff@2ndquadrant.com
Whole thread Raw
In response to Re: "unix_socket_directories" should be GUC_LIST_INPUT?  (Michael Paquier <michael@paquier.xyz>)
Responses Re: "unix_socket_directories" should be GUC_LIST_INPUT?
List pgsql-hackers
On 2020-10-23 10:02, Michael Paquier wrote:
>> So maybe we could get away with just changing it.  It'd be good to
>> verify though that this doesn't break existing string values for
>> the variable, assuming they contain no unlikely characters that'd
>> need quoting.
> 
> Yeah, that's the kind of things I wanted to check anyway before
> considering doing the switch.

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.)

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Prevent printing "next step instructions" in initdb and pg_upgrade
Next
From: Amit Kapila
Date:
Subject: Re: deferred primary key and logical replication