Re: predefined role(s) for VACUUM and ANALYZE
От | Kyotaro Horiguchi |
---|---|
Тема | Re: predefined role(s) for VACUUM and ANALYZE |
Дата | |
Msg-id | 20220726.105814.1865767063273092983.horikyota.ntt@gmail.com обсуждение исходный текст |
Ответ на | Re: predefined role(s) for VACUUM and ANALYZE (Kyotaro Horiguchi <horikyota.ntt@gmail.com>) |
Список | pgsql-hackers |
At Tue, 26 Jul 2022 10:47:12 +0900 (JST), Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote in > WARNING: skipping "pg_statistic" --- only superusers, roles with privileges of pg_vacuum_analyze, or the database ownercan vacuum it > WARNING: skipping "pg_type" --- only superusers, roles with privileges of pg_vacuum_analyze, or the database owner canvacuum it > <snip many lines> > WARNING: skipping "user_mappings" --- only table or database owner can vacuum it By the way, the last error above dissapears by granting pg_vacuum_analyze to the role. Is there a reason the message is left alone? And If I specified the view directly, I would get the following message. postgres=> vacuum information_schema.user_mappings; WARNING: skipping "user_mappings" --- cannot vacuum non-tables or special system tables So, "VACUUM;" does something wrong? Or is it the designed behavior? regards. -- Kyotaro Horiguchi NTT Open Source Software Center
В списке pgsql-hackers по дате отправления: