Re: Expand the use of check_canonical_path() for more GUCs

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: 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-05-19 11:02:12
Message-ID: e8fdcee5-bfef-7707-a704-35bac35e5a11@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020-05-19 09:09, Michael Paquier wrote:
> While digging into my backlog, I have found this message from Peter E
> mentioning about $subject:
> https://www.postgresql.org/message-id/e6aac026-174c-9952-689f-6bee76f9ab68@2ndquadrant.com
>
> It seems to me that it would be a good idea to make those checks more
> consistent, and attached is a patch.

That thread didn't resolve why check_canonical_path() is necessary
there. Maybe the existing uses could be removed?

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2020-05-19 11:02:57 Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions
Previous Message Etsuro Fujita 2020-05-19 10:35:56 Re: Optimizer docs typos