Re: Delegating superuser tasks to new security roles (Was: Granting control of SUSET gucs to non-superusers)
От | Mark Dilger |
---|---|
Тема | Re: Delegating superuser tasks to new security roles (Was: Granting control of SUSET gucs to non-superusers) |
Дата | |
Msg-id | 8A646633-0E51-470E-AB16-366AAA89B00F@enterprisedb.com обсуждение исходный текст |
Ответ на | Re: Delegating superuser tasks to new security roles (Was: Granting control of SUSET gucs to non-superusers) (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>) |
Ответы |
Re: Delegating superuser tasks to new security roles (Was: Granting control of SUSET gucs to non-superusers)
|
Список | pgsql-hackers |
> On Oct 6, 2021, at 10:48 PM, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> wrote: > > Hi Mark, thanks for this work. I'm late to be here in this thread, > please note that I didn't go through the entire thread as it is quite > long for me to read. Thanks for joining. > I have a question: it looks like the view pg_backend_memory_contexts > and the function pg_log_backend_memory_contexts are superuser only. > Isn't it a good idea to allow users with a pg_monitor or some other > similar role to use these as well? This question may be unrelated here > but I'm curious to know whether your patch set has a solution. Possibly, but I have stopped adding new topics to this particular patch set, as I'm already getting requests to break itinto separate sets and email threads. — Mark Dilger EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: