Re: RFC: Additional Directory for Extensions

From: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
To: Gabriele Bartolini <gabriele(dot)bartolini(at)enterprisedb(dot)com>
Cc: Matheus Alcantara <matheusssilv97(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Craig Ringer <craig(dot)ringer(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, 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: 2025-03-03 15:05:18
Message-ID: EFE22B1C-C193-4738-B21A-72E3F489EFD3@justatheory.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mar 3, 2025, at 08:39, Gabriele Bartolini <gabriele(dot)bartolini(at)enterprisedb(dot)com> wrote:

> As promised, here is a blog article that provides more context and information about what this feature will mean in Kubernetes with CloudNativePG: https://www.gabrielebartolini.it/articles/2025/03/the-immutable-future-of-postgresql-extensions-in-kubernetes-with-cloudnativepg/

Very nice writeup, thank you. Makes me wish for the bandwidth to get back to and start refining the PGXN OCI RFC to specify tags and/or metadata for the distribution of different contents, including:

* Full extension distribution (as currently written)
* Distribution with only pkglibdir and sharedir contents
* Distribution with only pkglibdir contents
* Distribution with only sharedir contents

I think we could come up with a standard that would work very nicely for a variety of use cases.

Will have to see if I can scrounge up the time for it.

Best,

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2025-03-03 15:10:44 Re: RFC: Additional Directory for Extensions
Previous Message Melanie Plageman 2025-03-03 14:40:00 Re: Introduce "log_connection_stages" setting.