Re: Allow pg_signal_backend members to use pg_log_backend_memory_stats().
От | Bossart, Nathan |
---|---|
Тема | Re: Allow pg_signal_backend members to use pg_log_backend_memory_stats(). |
Дата | |
Msg-id | 5B3B3232-14FC-4A90-84BD-4ABA78D2898B@amazon.com обсуждение исходный текст |
Ответ на | Re: Allow pg_signal_backend members to use pg_log_backend_memory_stats(). (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>) |
Список | pgsql-hackers |
On 10/25/21, 2:21 AM, "Bharath Rupireddy" <bharath.rupireddyforpostgres@gmail.com> wrote: > On Mon, Oct 25, 2021 at 12:40 PM Michael Paquier <michael@paquier.xyz> wrote: >> Hmm. Why don't you split the patch into two parts that can be >> discussed separately then? There would be one to remove all the >> superuser() checks you can think of, and a potential second to grant >> those function's execution to some system role. > > IMO, in this thread we can focus on remvong the > pg_log_backend_memory_contexts()'s superuser() check and +1 to start a > separate thread to remove superuser() checks for the other functions > and REVOKE the permissions in appropriate places, for system functins > system_functions.sql files, for extension functions, the extension > installation .sql files. See [1] and [2]. I like the general idea of removing hard-coded superuser checks first and granting execution to predefined roles second. I don't have any strong opinion about what should be done in this thread and what should be done elsewhere. Nathan
В списке pgsql-hackers по дате отправления: