Re: Allow relocatable extension to use @extschema@? - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: Allow relocatable extension to use @extschema@?
Date
Msg-id CAPpHfdsZvkikpRNcA41Qqvmncer20w1XLe=E=eWq_MoRXWVwEw@mail.gmail.com
Whole thread Raw
In response to Re: Allow relocatable extension to use @extschema@?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Dec 3, 2019 at 6:18 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Alexander Korotkov <a.korotkov@postgrespro.ru> writes:
> > But nevertheless should we allow relocatable extension to use
> > @extschema@.  Any thoughts?
>
> No.  The reasoning in the comment still holds good: if you embed
> @extschema@ in an object's definition, it becomes nonrelocatable.

I see, allowing @extschema@ in non-relocatable extension provides easy
way to shoot yourself in the foot.

However, it might be still useful to be able to distinguish extension
and core object in upgrade script of relocatable extensions.  What
about (optional) way to set search_path to @extschema@, pg_catalog
instead of just @extschema@?

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: [HACKERS] Block level parallel vacuum
Next
From: Masahiko Sawada
Date:
Subject: Re: [HACKERS] Block level parallel vacuum