Message-ID: <6788b6c5.df0a0220.12545e.47be@mx.google.com>
Sender: Michael Banck <mbanck@gmail.com>
Date: Thu, 16 Jan 2025 08:35:32 +0100
From: Michael Banck <mbanck@gmx.net>
To: Shinya Kato <shinya11.kato@gmail.com>
Cc: Kirill Reshke <reshkekirill@gmail.com>,
	Jelte Fennema-Nio <postgres@jeltef.nl>,
	PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: [PATCH] New predefined role pg_manage_extensions
References: <65a1524e.050a0220.49266.7670@mx.google.com>
 <CAGECzQQ2HB85N9PjTAdDTpFCciQmpeE2PcXbc8EKhSF=RPi3fA@mail.gmail.com>
 <65a247d9.050a0220.ecb2e.1177@mx.google.com>
 <6723fae4.a70a0220.28a8f2.27e4@mx.google.com>
 <CALdSSPi+9htTHtgm+y92uUgEEovhur5URkXDMCpR=ZqmQbxHhQ@mail.gmail.com>
 <6773d26a.050a0220.326c12.b02a@mx.google.com>
 <CAOzEurSGnvW3TyyHqBgS_cPr+SGc_DHa3B5_cfSJ66VzsOoEnw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAOzEurSGnvW3TyyHqBgS_cPr+SGc_DHa3B5_cfSJ66VzsOoEnw@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://www.postgresql.org/message-id/6788b6c5.df0a0220.12545e.47be%40mx.google.com>
Precedence: bulk

Hi,

On Thu, Jan 16, 2025 at 04:09:44PM +0900, Shinya Kato wrote:
> On Thu, Jan 16, 2025 at 3:31 PM Michael Banck <mbanck@gmx.net> wrote:
> > I do think having a whitelist of allowed-to-be-installed extensions
> > (similar/like https://github.com/dimitri/pgextwlist) makes sense
> > additionally in today's container/cloud word where the local Postgres
> > admin might not have control over which packages get installed but wants
> > to have control over which extension the application admins (or whoever)
> > may create, but that is another topic I think.
> 
> To use a certain extension, you may need to install the
> postgresql-contrib package. In that case, is there a way to restrict
> extensions other than the required one? Or is it unnecessary to impose
> such restrictions?

I was thinking about the following (increasinly common, I think)
use-case: we have a largish organisation where the platform/whatever
team wants to deploy Postgres in a uniform way and install the common
set of all contrib and external extensions that might be needed for each
instance. But then you have instance-specific admins that might want to
restrict the set of extensions their instance (or their developers/app
admins/whatever) is allowed to use. However, this is not the purpose of
the patch in discussion, just a side-remark that this functionality
would be good to have in addition.


Michael