Re: predefined role(s) for VACUUM and ANALYZE - Mailing list pgsql-hackers

From Kyotaro Horiguchi
Subject Re: predefined role(s) for VACUUM and ANALYZE
Date
Msg-id 20220726.105814.1865767063273092983.horikyota.ntt@gmail.com
Whole thread Raw
In response to Re: predefined role(s) for VACUUM and ANALYZE  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
List 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 by date:

Previous
From: Zhang Mingli
Date:
Subject: Re: optimize lookups in snapshot [sub]xip arrays
Next
From: Fujii Masao
Date:
Subject: Re: Remove useless arguments in ReadCheckpointRecord().