Re: Ability to reference other extensions by schema in extension scripts
От | 'Sandro Santilli' |
---|---|
Тема | Re: Ability to reference other extensions by schema in extension scripts |
Дата | |
Msg-id | 20230313115916.ivvg4tj54szeu5rj@c19 обсуждение исходный текст |
Ответ на | RE: Ability to reference other extensions by schema in extension scripts ("Regina Obe" <lr@pcorp.us>) |
Ответы |
RE: Ability to reference other extensions by schema in extension scripts
RE: Ability to reference other extensions by schema in extension scripts |
Список | 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 given 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 no_relocate (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 putting them in no_relocate. This may be intentional, as some substitutions may not 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 https://strk.kbt.io/services.html
В списке pgsql-hackers по дате отправления: