Re: RFC: Additional Directory for Extensions
От | Craig Ringer |
---|---|
Тема | Re: RFC: Additional Directory for Extensions |
Дата | |
Msg-id | CAGRY4nztcRfqkdKy9ODbgUEQ=2ZVwovpkAK5CvWpQShoMj1AzQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: RFC: Additional Directory for Extensions (Craig Ringer <craig.ringer@enterprisedb.com>) |
Список | pgsql-hackers |
On Fri, 23 Aug 2024 at 10:14, Craig Ringer <craig.ringer@enterprisedb.com> wrote: > On Thu, 22 Aug 2024 at 21:00, Gabriele Bartolini > <gabriele.bartolini@enterprisedb.com> wrote: > > On Thu, 22 Aug 2024 at 09:32, Jelte Fennema-Nio <postgres@jeltef.nl> wrote: > >> SET extension_search_path = /mnt/extensions/pg16/* > > > > That'd be great. +1. > > Agreed, that'd be handy, but not worth blocking the underlying capability for. > > Except possibly to the degree that the feature should reserve wildcard > characters and require them to be escaped if they appear on a path, so > there's no BC break if it's added later. ... though on second thoughts, it might make more sense to just recursively search directories found under each path entry. Rules like 'search if a redundant trailing / is present' can be an option. That way there's no icky path escaping needed for normal configuration.
В списке pgsql-hackers по дате отправления: