Re: Is there a way around function search_path killing SQL function inlining? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Is there a way around function search_path killing SQL function inlining?
Date
Msg-id CA+TgmoYo1eR3011SLSbm2K+4X4RtYGuDuhNSkuYMgH7fomMCRg@mail.gmail.com
Whole thread Raw
In response to Is there a way around function search_path killing SQL function inlining?  ("Regina Obe" <lr@pcorp.us>)
Responses Re: Is there a way around function search_path killing SQL function inlining?
List pgsql-hackers
On Fri, Mar 4, 2016 at 9:29 PM, Regina Obe <lr@pcorp.us> wrote:
> I think the answer to this question is NO, but thought I'd ask.
>
> A lot of folks in PostGIS land are suffering from restore issues,
> materialized view issues etc. because we have functions such as
>
> ST_Intersects
>
> Which does _ST_Intersects  AND &&
>
> Since _ST_Intersects is not schema qualified, during database restore (which
> sets the schema to the table or view schema), materialized views that depend
> on this do not come back.

Could you provide a self-contained, reproducible test case that
illustrates this problem?  Ideally, one that doesn't involve
installing PostGIS?

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: CustomScan in a larger structure (RE: CustomScan support on readfuncs.c)
Next
From: Tom Lane
Date:
Subject: Re: Splitting lengthy sgml files