| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Expand the use of check_canonical_path() for more GUCs |
| Date: | 2020-06-03 16:16:08 |
| Message-ID: | CA+TgmobH=wmVgfCzKjwgiJEWDFJO923pWpsgi6EJQrBmFHoZpQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 2, 2020 at 5:04 AM Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> The archeology reveals that these calls where originally added to
> canonicalize the data_directory and config_file settings (7b0f060d54),
> but that was then moved out of guc.c to be done early during postmaster
> startup (337ffcddba). The remaining calls of check_canonical_path() in
> guc.c appear to be leftovers from a previous regime.
Thanks for looking into it. Sounds like it can just be ripped out,
then, unless someone knows of a reason to do otherwise.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martín Marqués | 2020-06-03 16:32:28 | Re: Read access for pg_monitor to pg_replication_origin_status view |
| Previous Message | Robert Haas | 2020-06-03 16:13:14 | Re: Parallel copy |