Re: Potential problem in commit f777d773878 and 4f7f7b03758
От | Srinath Reddy Sadipiralla |
---|---|
Тема | Re: Potential problem in commit f777d773878 and 4f7f7b03758 |
Дата | |
Msg-id | CAFC+b6rU-Qy5u-eZRiObOdp-AzL0gKWr-R6LwSyyircBf3a-5Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Potential problem in commit f777d773878 and 4f7f7b03758 (Srinath Reddy Sadipiralla <srinath2133@gmail.com>) |
Список | pgsql-hackers |
On Sun, Aug 24, 2025 at 5:58 PM Srinath Reddy Sadipiralla <srinath2133@gmail.com> wrote:
Hi,
Thanks Dilip and Matheus for working on this , i reviewed the latest patch given my Matheus and it LGTM but i have doubt that in f777d773878 commit the $libdir was moved out from expand_dynamic_library_name into load_external_function because if someone specifies LOAD '$libdir/foo' explicitly they want to get the foo.so from $libdir not from other paths given in dynamic_library_path ,i think same should go for the case when we do "create extension" will try to execute the sql script which will replace the MODULE_PATHNAME with module_pathname from .control file lets say which is $libdir/foo ,now during the sql functions execution this calls the load_external_function where we strip $libdir and we are going to load the foo.so from other paths specified in dynamic_library_path, isn't that a problem , i think this case is also same as with the LOAD.
sorry i missed to mention "stripping of $libdir" here " but i have a doubt that in f777d773878 commit the stripping of $libdir was moved out from expand_dynamic_library_name into load_external_function "
В списке pgsql-hackers по дате отправления: