Re: RFC: Additional Directory for Extensions

From: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
To: Matheus Alcantara <matheusssilv97(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Gabriele Bartolini <gabriele(dot)bartolini(at)enterprisedb(dot)com>, Craig Ringer <craig(dot)ringer(at)enterprisedb(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: 2025-03-21 22:05:34
Message-ID: 0F50D989-B82D-4F59-9F13-C08A4673322C@justatheory.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Mar 21, 2025, at 17:52, Matheus Alcantara <matheusssilv97(at)gmail(dot)com> wrote:

> Did you miss to attach the patch?

No. You can see it in the archive[1]. Direct link[2].

> Maybe we could make the "extension" part of the extension control path
> explicitly, like Peter has mentioned in his first patch version [1]?.
> If "directory" is not set we could use "extension" otherwise use the
> "directory" as a path suffix when searching on extension_control_path?

So, omit “extension” from the path options, append it to search for control files, and then append the directory value (if not absolute) if it exists to look for files, and otherwise append “extensions” to find them, too. I think that makes sense.

Essentially it becomes a SHAREDIR search path.

Best,

David

[1]: https://postgr.es/m/6B5BF07B-8A21-48E3-858C-1DC22F3A28B4@justatheory.com
[2]: https://www.postgresql.org/message-id/attachment/174397/v1-0001-Flesh-out-docs-for-the-prefix-make-variable.patch

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-03-21 22:45:51 Re: query_id: jumble names of temp tables for better pg_stat_statement UX
Previous Message Melanie Plageman 2025-03-21 21:54:50 Re: Using read_stream in index vacuum