Re: Ability to reference other extensions by schema in extension scripts
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Regina Obe" <lr@pcorp.us>
Cc: "'Gregory Stark \(as CFM\)'" <stark.cfm@gmail.com>,
"'Sandro Santilli'" <strk@kbt.io>, pgsql-hackers@lists.postgresql.org,
"'Regina Obe'" <r@pcorp.us>
Date: 2023-03-10T22:14:36Z
Lists: pgsql-hackers
"Regina Obe" <lr@pcorp.us> writes: >> If you want to work harder, perhaps a reasonable way to deal with the issue >> would be to allow dependent extensions to declare that they don't want your >> extension relocated. But I do not think it's okay to make that the default >> behavior, much less the only behavior. > - the main issue I ran into is I have to introduce another dependency type > or go with Sandro's idea of using refsubobjid for this purpose. No, pg_depend is not the thing to use for this. I was thinking of a new field in the extension's control file, right beside where it says it's dependent on such-and-such extensions in the first place. Say like requires = 'extfoo, extbar' no_relocate = 'extfoo' > So you are proposing I change the execute_extension_scripts input args to > take more args? Why not? It's local to that file, so you won't break anything. regards, tom lane
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add @extschema:name@ and no_relocate options to extensions.
- 72a5b1fc8804 16.0 landed
-
pkg-config Requires.private entries should be comma-separated
- 4ef1be5a0b67 16.0 cited
-
Fix logic buglets in pg_dump's flagInhAttrs().
- 128dd9f9eca0 16.0 cited