Postgres Pro
Downloads
Home   >   mailing lists

Re: Expand the use of check_canonical_path() for more GUCs - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Expand the use of check_canonical_path() for more GUCs
Date
Msg-id CA+TgmoZRC+NQB8jsumh5U2+xEs1TvVdr9CkAVkAybbw-4ew92Q@mail.gmail.com
Whole thread Raw
In response to Re: Expand the use of check_canonical_path() for more GUCs  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Expand the use of check_canonical_path() for more GUCs  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
Tree view 
On Tue, May 19, 2020 at 7:02 AM Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> That thread didn't resolve why check_canonical_path() is necessary
> there.  Maybe the existing uses could be removed?

This first sentence of this reply seems worthy of particualr
attention. We have to know what problem this is intended to fix before
we try to decide in which cases it's needed. Otherwise, whether we add
it everywhere or remove it everywhere, we'll only know that it's
consistent, not that it's correct.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Chapman Flack
Date:
Subject: Re: pie-in-sky idea: 'sensitive' function parameters
Next
From: "David G. Johnston"
Date:
Subject: Re: pg_dump fail to not dump public schema orders