Re: Is there a way around function search_path killing SQL function inlining?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Regina Obe <lr(at)pcorp(dot)us>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Is there a way around function search_path killing SQL function inlining?
Date: 2016-03-07 15:07:34
Message-ID: CA+TgmoYo1eR3011SLSbm2K+4X4RtYGuDuhNSkuYMgH7fomMCRg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 4, 2016 at 9:29 PM, Regina Obe <lr(at)pcorp(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-03-07 15:09:57 Re: Splitting lengthy sgml files
Previous Message Robert Haas 2016-03-07 15:06:11 Re: CustomScan in a larger structure (RE: CustomScan support on readfuncs.c)