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

From Noah Misch
Subject Re: Allow relocatable extension to use @extschema@?
Date
Msg-id 20200118182821.GA2735013@rfd.leadboat.com
Whole thread Raw
In response to Re: Allow relocatable extension to use @extschema@?  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Thu, Dec 05, 2019 at 09:52:50AM -0500, Robert Haas wrote:
> On Tue, Dec 3, 2019 at 10:18 AM 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.
> 
> That's demonstrably false, and the links included in the OP prove it.

Right.  Or, to add further precision, embedding @extschema@ persistently in
the system catalogs does make the extension nonrelocatable.  The OP examples
merely embed @extschema@ in extension scripts, and they don't impair
relocation.  I'm okay with the proposal, but I still wouldn't mind deprecating
relocatable=true.



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: SQL/JSON: functions
Next
From: Andres Freund
Date:
Subject: Re: should crash recovery ignore checkpoint_flush_after ?