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

From: "Regina Obe" <lr(at)pcorp(dot)us>
To: <strk(at)kbt(dot)io>
Cc: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'Gregory Stark \(as CFM\)'" <stark(dot)cfm(at)gmail(dot)com>, <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "'Regina Obe'" <r(at)pcorp(dot)us>
Subject: RE: Ability to reference other extensions by schema in extension scripts
Date: 2023-03-13 21:57:57
Message-ID: 000701d955f6$dfaaf8a0$9f00e9e0$
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> On Sat, Mar 11, 2023 at 03:18:18AM -0500, Regina Obe wrote:
> > Attached is a revised patch with these changes in place.
> I've given a try to this patch. It builds and regresses fine.
> My own tests also worked fine. As long as ext1 was found in the ext2's
> no_relocate list it could not be relocated, and proper error message is
> to user trying it.
> Nitpicking, there are a few things that are weird to me:
> 1) I don't get any error/warning if I put an arbitrary string into
> (there's no check to verify the no_relocate is a subset of the requires).
> 2) An extension can still reference extensions it depends on without
> them in no_relocate. This may be intentional, as some substitutions may
> require blocking relocation, but felt inconsistent with the normal
> @extschema@ which is never replaced unless an extension is marked as non-
> relocatable.
> --strk;
> Libre GIS consultant/developer

Attached is a slightly revised patch to fix the extra whitespace in the
document that Sandro noted to me.


Attachment Content-Type Size
0007-Allow-use-of-extschema-reqextname-to-reference.patch application/octet-stream 20.9 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2023-03-13 21:59:19 Re: Microsecond-based timeouts
Previous Message Tomas Vondra 2023-03-13 21:47:12 Re: Add LZ4 compression in pg_dump