Re: predefined role(s) for VACUUM and ANALYZE

Поиск
Список
Период
Сортировка
От Nathan Bossart
Тема Re: predefined role(s) for VACUUM and ANALYZE
Дата
Msg-id 20220725164049.GA4091959@nathanxps13
обсуждение исходный текст
Ответ на Re: predefined role(s) for VACUUM and ANALYZE  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Ответы Re: predefined role(s) for VACUUM and ANALYZE  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Список pgsql-hackers
On Mon, Jul 25, 2022 at 12:58:36PM +0530, Bharath Rupireddy wrote:
> Thanks. I'm personally happy with more granular levels of control (as
> we don't have to give full superuser access to just run a few commands
> or maintenance operations) for various postgres commands. The only
> concern is that we might eventually end up with many predefined roles
> (perhaps one predefined role per command), spreading all around the
> code base and it might be difficult for the users to digest all of the
> roles in. It will be great if we can have some sort of rules or
> methods to define a separate role for a command.

Yeah, in the future, I could see this growing to a couple dozen predefined
roles.  Given they are relatively inexpensive and there are already 12 of
them, I'm personally not too worried about the list becoming too unwieldy.
Another way to help users might be to create additional aggregate
predefined roles (like pg_monitor) for common combinations.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Nathan Bossart
Дата:
Сообщение: Re: Pre-allocating WAL files
Следующее
От: Hamid Akhtar
Дата:
Сообщение: Re: explain analyze rows=%.0f