From: "Regina Obe" <lr@pcorp.us>
To: <pgsql-hackers@postgresql.org>
Subject: Ability to reference other extensions by schema in extension scripts
Date: Wed, 9 Nov 2022 21:43:43 -0500
Message-ID: <003001d8f4ae$402282c0$c0678840$@pcorp.us>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Adj0rQxwug+M9ce1Rae/qiowRn2G5A==
Content-Language: en-us
Archived-At: 
 <https://www.postgresql.org/message-id/003001d8f4ae%24402282c0%24c0678840%24%40pcorp.us>
Precedence: bulk

I think I had brought this up a while ago, but I forget what the opinion was
on the matter.

PostGIS has a number of extensions that rely on it.  For the extensions that
are packaged with PostGIS, we force them all into the same schema except for
the postgis_topology and postgis_tiger_geocoder extensions which are already
installed in dedicated schemas.

This makes it impossible for postgis_topology and postgis_tiger_geocoder to
schema qualify their use of postgis.  Other extensions like pgRouting,
h3-pg, mobilitydb have similar issues.

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 file.

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.

The extension plumbing will then use this information to look up the schema
that the current required extensions are installed in, and replace the
variables with the schema of where the dependent extension is installed.

Does anyone see any issue with this idea. 

Thanks,
Regina