RE: Ability to reference other extensions by schema in extension scripts

From: "Regina Obe" <lr(at)pcorp(dot)us>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: RE: Ability to reference other extensions by schema in extension scripts
Date: 2022-11-10 04:44:07
Message-ID: 004501d8f4bf$1213fba0$363bf2e0$
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> "Regina Obe" <lr(at)pcorp(dot)us> writes:
> > My proposal is this. If you think it's a good enough idea I can work
> > up a patch for this.
> > Extensions currently are allowed to specify a requires in the control
> > I propose to use this information, to allow replacement of phrases
> > @extschema_nameofextension@ as a variable, where nameofextension has
> > to be one of the extensions listed in the requires.
> I have a distinct sense of deja vu here. I think this idea, or something
> isomorphic to it, was previously discussed with some other syntax details.
> I'm too lazy to go searching the archives right now, but I suggest that
you try to
> find that discussion and see if the discussed syntax seems better or worse
> what you mention.
> I think it might've been along the line of @extschema:nameofextension@,
> which seems like it might be superior because colon isn't a valid
> character so there's less risk of ambiguity.
> regards, tom lane
I found the old discussion I recalled having and Stephen had suggested using


On this thread --

Is that the one you remember?


In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Yugo NAGATA 2022-11-10 04:49:19 Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
Previous Message Michael Paquier 2022-11-10 04:37:57 Re: Tests for psql \g and \o