From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Regina Obe" <lr@pcorp.us>
cc: pgsql-hackers@postgresql.org
Subject: Re: Ability to reference other extensions by schema in extension
 scripts
In-reply-to: <004501d8f4bf$1213fba0$363bf2e0$@pcorp.us>
References: <003001d8f4ae$402282c0$c0678840$@pcorp.us>
 <79300.1668052170@sss.pgh.pa.us> <004501d8f4bf$1213fba0$363bf2e0$@pcorp.us>
Comments: In-reply-to "Regina Obe" <lr@pcorp.us>
	message dated "Wed, 09 Nov 2022 23:44:07 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <175297.1668101858.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 10 Nov 2022 12:37:38 -0500
Message-ID: <175298.1668101858@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/175298.1668101858%40sss.pgh.pa.us>
Precedence: bulk

"Regina Obe" <lr@pcorp.us> writes:
>> I have a distinct sense of deja vu here.  I think this idea, or somethi=
ng
>> isomorphic to it, was previously discussed with some other syntax detai=
ls.

> I found the old discussion I recalled having and Stephen had suggested u=
sing
> @extschema{'postgis'}@
> On this thread --
> https://www.postgresql.org/message-id/20160425232251.GR10850@tamriel.sno=
wman.net
> Is that the one you remember?

Hmmm ... no, ISTM it was considerably more recent than that.
[ ...digs... ]  Here we go, it was in the discussion around
converting contrib SQL functions to new-style:

https://www.postgresql.org/message-id/flat/3395418.1618352794%40sss.pgh.pa=
.us

There are a few different ideas bandied around in there.
Personally I still like the @extschema:extensionname@
option the best, though.

			regards, tom lane