From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
---|---|
To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
Cc: | 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-06-26 09:36:27 |
Message-ID: | CAGECzQSkhB_GOs2EmvghPrTcYmC8TOkkDDS=Ws4Vw-=Q4T+KBw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 25 Jun 2024 at 19:33, David E. Wheeler <david(at)justatheory(dot)com> wrote:
>
> On Jun 24, 2024, at 5:32 PM, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> wrote:
>
> > Still, for the sake of completeness it might make sense to support
> > this whole list in extension_destdir. (assuming it's easy to do)
>
> It should be with the current patch, which just uses a prefix to paths in `pg_config`.
Ah alright, I think it confused me because I never saw bindir being
used. But as it turns out the current backend code never uses bindir.
So that makes sense. I guess to actually use the binaries from the
extension_destdir/$BINDIR the operator needs to set PATH accordingly,
or the extension needs to be changed to support extension_destdir.
It might be nice to add a helper function to find binaries in BINDIR,
now that the resolution logic is more complex. Even if postgres itself
doesn't use it. That would make it easier for extensions to be
modified to support extension_distdir. Something like
find_bindir_executable(char *name)
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiro.Ikeda | 2024-06-26 10:22:23 | RE: Parallel Bitmap Heap Scan reports per-worker stats in EXPLAIN ANALYZE |
Previous Message | Jelte Fennema-Nio | 2024-06-26 09:30:39 | Re: RFC: Additional Directory for Extensions |