| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, 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 16:19:14 |
| Message-ID: | CA+TgmoYZuc-UNnxqwOVK2hXhMnujsCesk32ExhYnE6y91X=_PA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 27, 2020 at 9:45 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-10-27 16:23:22 | Re: "unix_socket_directories" should be GUC_LIST_INPUT? |
| Previous Message | Adam Brusselback | 2020-10-27 16:14:52 | Re: Implementing Incremental View Maintenance |