Re: RFC: Additional Directory for Extensions - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: RFC: Additional Directory for Extensions
Date
Msg-id 0F50D989-B82D-4F59-9F13-C08A4673322C@justatheory.com
Whole thread Raw
In response to Re: RFC: Additional Directory for Extensions  (Matheus Alcantara <matheusssilv97@gmail.com>)
List pgsql-hackers
On Mar 21, 2025, at 17:52, Matheus Alcantara <matheusssilv97@gmail.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
(ifnot absolute) if it exists to look for files, and otherwise append “extensions” to find them, too. I think that
makessense. 

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


Attachment

pgsql-hackers by date:

Previous
From: Melanie Plageman
Date:
Subject: Re: Using read_stream in index vacuum
Next
From: Michael Paquier
Date:
Subject: Re: query_id: jumble names of temp tables for better pg_stat_statement UX