Horton

Re: RFC: Additional Directory for Extensions

David E. Wheeler <david@justatheory.com>

View thread View on postgr.es
From: "David E. Wheeler" <david@justatheory.com>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: Craig Ringer <craig.ringer@enterprisedb.com>, Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>, Robert Haas <robertmhaas@gmail.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2024-11-20T18:04:17Z
Lists: pgsql-hackers 
On Nov 20, 2024, at 04:05, Peter Eisentraut <peter@eisentraut.org> wrote:

> The path is only consulted if the specified name does not contain a slash.  So if you do LOAD 'foo', the path is consulted, but if you do LOAD '$libdir/foo', it is not.  The problem I'm describing is that most extensions use the latter style, per current recommendation in the documentation.

I see; some details here:

  https://www.postgresql.org/docs/current/xfunc-c.html#XFUNC-C-DYNLOAD

And I suppose the `directory` control file variable and `MODULEDIR` make variable make that necessary. 

Maybe $libdir should be stripped out when installing extensions to work with this patch?

Best,

David

Commits

  1. doc: Flesh out extension docs for the "prefix" make variable

  2. Fix extension control path tests

  3. extension_control_path