From: | Craig Ringer <craig(dot)ringer(at)enterprisedb(dot)com> |
---|---|
To: | Gabriele Bartolini <gabriele(dot)bartolini(at)enterprisedb(dot)com> |
Cc: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: RFC: Additional Directory for Extensions |
Date: | 2024-08-22 22:14:20 |
Message-ID: | CAGRY4nypoaR_v3CiTyAROjYZ5Hm=S6L3MPQv3D1=L_CFNGy_LA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 22 Aug 2024 at 21:00, Gabriele Bartolini
<gabriele(dot)bartolini(at)enterprisedb(dot)com> wrote:
> On Thu, 22 Aug 2024 at 09:32, Jelte Fennema-Nio <postgres(at)jeltef(dot)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.
On Thu, 22 Aug 2024 at 21:00, Gabriele Bartolini
<gabriele(dot)bartolini(at)enterprisedb(dot)com> wrote:
>
> Hi Jelte,
>
> On Thu, 22 Aug 2024 at 09:32, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> wrote:
>>
>> It looks like you want one directory per extension, so that list would
>> get pretty long if you have multiple extensions. Maybe (as a follow up
>> change), we should start to support a * as a wildcard in both of these
>> GUCs. So you could say:
>>
>> SET extension_search_path = /mnt/extensions/pg16/*
>>
>> To mean effectively the same as you're describing above.
>
>
> That'd be great. +1.
>
> --
> Gabriele Bartolini
> Vice President, Cloud Native at EDB
> enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2024-08-22 22:16:00 | Re: RFC: Additional Directory for Extensions |
Previous Message | Daniel Gustafsson | 2024-08-22 21:13:15 | Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~? |