| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fixes for missing schema qualifications |
| Date: | 2018-03-14 02:54:33 |
| Message-ID: | 20180314025433.GJ1150@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 13, 2018 at 07:30:23PM -0700, David G. Johnston wrote:
> On Tue, Mar 13, 2018 at 6:50 PM, Michael Paquier <michael(at)paquier(dot)xyz>
> wrote:
>> To simplify user's life, we
>> could also recommend just to users to issue a ALTER FUNCTION SET
>> search_path to fix the problem for all functions, that's easier to
>> digest.
>
> I'm unclear as to what scope you are suggesting the above advice (and
> option #1) apply to. All pg_catalog/information_schema functions or all
> functions including those created by users?
>
I am suggesting that to keep simple the release notes of the next minor
versions, but still patch information_schema.sql with the changes based
on operator(pg_catalog.foo) for all functions internally as as new
deployments get the right call.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuro Yamada | 2018-03-14 03:26:54 | planner bug regarding lateral and subquery? |
| Previous Message | David G. Johnston | 2018-03-14 02:30:23 | Re: Fixes for missing schema qualifications |