Re: RFC: Extension Packaging & Lookup

From: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: Gabriele Bartolini <gabriele(dot)bartolini(at)enterprisedb(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Christoph Berg <myon(at)debian(dot)org>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: RFC: Extension Packaging & Lookup
Date: 2024-11-25 21:45:59
Message-ID: C5759036-4F1F-468A-86D6-F8ECC6716EE1@justatheory.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Nov 13, 2024, at 16:38, David E. Wheeler <david(at)justatheory(dot)com> wrote:

> I came to this thinking that it was important to keep core (contrib, PL) extensions separate from non-core extensions, and if so, it’d be useful to have other defaults so that `make install` would go to the right one (site by default).
>
> But maybe it’s not necessary? If there are no extensions by default, perhaps it doesn’t matter?

I ripped out the core/vendor/site stuff and have now published a fairly detailed RFC.

https://justatheory.com/2024/11/rfc-extension-packaging-lookup/

What do you think, Hacker Friends?

Best,

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ilia Evdokimov 2024-11-25 22:15:25 Re: Sample rate added to pg_stat_statements
Previous Message Tom Lane 2024-11-25 21:39:13 Re: Self contradictory examining on rel's baserestrictinfo