Re: "unix_socket_directories" should be GUC_LIST_INPUT?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Ian Lawrence Barwick <barwick(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: "unix_socket_directories" should be GUC_LIST_INPUT?
Date: 2020-10-27 13:45:43
Message-ID: 1047465.1603806343@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-10-27 13:51:16 Re: duplicate function oid symbols
Previous Message Peter Eisentraut 2020-10-27 13:45:13 Re: SQL-standard function body