Re: RFC: Additional Directory for Extensions

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:16:00
Message-ID: CAGRY4nztcRfqkdKy9ODbgUEQ=2ZVwovpkAK5CvWpQShoMj1AzQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 23 Aug 2024 at 10:14, Craig Ringer
<craig(dot)ringer(at)enterprisedb(dot)com> wrote:
> 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.

... 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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message John H 2024-08-22 23:33:14 Re: Switching XLog source from archive to streaming when primary available
Previous Message Craig Ringer 2024-08-22 22:14:20 Re: RFC: Additional Directory for Extensions