Re: RFC: Additional Directory for Extensions

From: David E(dot) Wheeler <david(at)justatheory(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: 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-25 22:31:46
Message-ID: FE1622BC-81BB-487B-BF0A-4D29906F8F47@justatheory.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jun 25, 2024, at 10:43 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> If we want to work on making the sorts of changes that
> you're proposing, let's do it on a separate thread. It's not going to
> be meaningfully harder to move in that direction after some patch like
> this than it is today.

I appreciate this separation of concerns, Robert.

In other news, here’s an updated patch that expands the documentation to record that the destination directory is a prefix, and full paths should be used under it. Also take the opportunity to document the PGXS DESTDIR variable as the thing to use to install files under the destination directory.

It still requires a server restart; I can change it back to superuser-only if that’s the consensus.

For those who prefer a GitHub patch review experience, see this PR:

https://github.com/theory/postgres/pull/3/files

Best,

David

Attachment Content-Type Size
v4-0001-Add-extension_destdir-GUC.patch application/octet-stream 11.5 KB
unknown_filename text/plain 2 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message James Coleman 2024-06-25 23:05:04 Re: Should we document how column DEFAULT expressions work?
Previous Message Ahmed Yarub Hani Al Nuaimi 2024-06-25 22:12:44 Zero -downtime FULL VACUUM/clustering/defragmentation with zero-downtime and now extra disk space