Re: shoud be get_extension_schema visible?
От | Julien Rouhaud |
---|---|
Тема | Re: shoud be get_extension_schema visible? |
Дата | |
Msg-id | 20230306073331.eoe46aibinyoof5k@jrouhaud обсуждение исходный текст |
Ответ на | Re: shoud be get_extension_schema visible? (Pavel Stehule <pavel.stehule@gmail.com>) |
Ответы |
Re: shoud be get_extension_schema visible?
|
Список | pgsql-hackers |
Hi, On Sun, Feb 19, 2023 at 06:40:39AM +0100, Pavel Stehule wrote: > > pá 17. 2. 2023 v 6:45 odesílatel Pavel Stehule <pavel.stehule@gmail.com> > napsal: > > > more times I needed to get the extension's assigned namespace. There is > > already a cooked function get_extension_schema, but it is static. > > > > I need to find a function with a known name, but possibly an unknown > > schema from a known extension. > > > > Here is an patch The patch is trivial so I don't have much to say about it, and it also seems quite reasonable generally. Note for other reviewers / committers: this is a something actually already wanted for 3rd party code. As an example, here's Pavel's code in plpgsql_check extension that internally has to duplicate this function (and deal with compatibility): https://github.com/okbob/plpgsql_check/blob/master/src/catalog.c#L205 I'm marking this entry as Ready For Committer.
В списке pgsql-hackers по дате отправления: