| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, walther(at)technowledgy(dot)de, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Christoph Berg <myon(at)debian(dot)org> |
| Subject: | Re: RFC: Additional Directory for Extensions |
| Date: | 2024-06-24 21:31:53 |
| Message-ID: | A3D50C61-64EB-4A42-B885-DBBBA045164C@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jun 24, 2024, at 17:17, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> wrote:
> If you want to only change $libdir during CREATE EXTENSION (or ALTER
> EXTENSION UPDATE), then why not just change it there. And really you'd
> only want to change it when creating an extension from which the
> control file is coming from extension_destdir.
IIUC, the postmaster needs to load an extension on first use in every session unless it’s in shared_preload_libraries.
> However, I can also see a case for really always changing $libdir.
> Because some extensions in shared_preload_libraries, might want to
> trigger loading other libraries that they ship with dynamically. And
> these libraries are probably also in extension_destdir.
Right, it can be more than just the DSOs for the extension itself.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jelte Fennema-Nio | 2024-06-24 21:32:20 | Re: RFC: Additional Directory for Extensions |
| Previous Message | Jelte Fennema-Nio | 2024-06-24 21:23:41 | Re: RFC: Additional Directory for Extensions |