Re: Predefined role pg_maintenance for VACUUM, ANALYZE, CHECKPOINT.
От | Jeff Davis |
---|---|
Тема | Re: Predefined role pg_maintenance for VACUUM, ANALYZE, CHECKPOINT. |
Дата | |
Msg-id | 1c3205584833be95e3225371f5b660f94088901d.camel@j-davis.com обсуждение исходный текст |
Ответ на | Re: Predefined role pg_maintenance for VACUUM, ANALYZE, CHECKPOINT. ("Bossart, Nathan" <bossartn@amazon.com>) |
Ответы |
Re: Predefined role pg_maintenance for VACUUM, ANALYZE, CHECKPOINT.
Re: Predefined role pg_maintenance for VACUUM, ANALYZE, CHECKPOINT. |
Список | pgsql-hackers |
On Sun, 2021-10-24 at 21:32 +0000, Bossart, Nathan wrote: > My initial reaction was that members of pg_maintenance should be able > to do all of these things (VACUUM, ANALYZE, CLUSTER, REINDEX, and > CHECKPOINT). What about REFRESH MATERIALIZED VIEW? That seems more specific to a workload, but it's hard to draw a clear line between that and CLUSTER. > Maybe one > option is to have two separate roles, one for commands that require > lower lock levels (i.e., ANALYZE and VACUUM without TRUNCATE and > FULL), and another for all of the maintenance commands. My main motivation is CHECKPOINT and database-wide VACUUM and ANALYZE. I'm fine extending it if others think it would be worthwhile, but it goes beyond my use case. Regards, Jeff Davis
В списке pgsql-hackers по дате отправления: