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

From Mark Dilger
Subject Re: predefined role(s) for VACUUM and ANALYZE
Date
Msg-id 27EAC430-8609-4BAB-9B30-31C485C32C11@enterprisedb.com
Whole thread Raw
In response to Re: predefined role(s) for VACUUM and ANALYZE  (Stephen Frost <sfrost@snowman.net>)
Responses Re: predefined role(s) for VACUUM and ANALYZE
List pgsql-hackers

> On Sep 7, 2022, at 4:09 PM, Stephen Frost <sfrost@snowman.net> wrote:
>
> Calling this a redesign is over-stating things, imv … and I’d much rather have the per-relation granularity than
predefinedroles for this, so there is that to consider too, perhaps. 

Ok, now I'm a bit lost.  If I want to use Nathan's feature to create a role to vacuum and analyze my database on a
regularbasis, how does per-relation granularity help me?  If somebody creates a new table and doesn't grant those
privilegesto the role, doesn't that break the usage case?  To me, per-relation granularity sounds useful, but
orthogonal,to this feature. 

—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company






pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: predefined role(s) for VACUUM and ANALYZE
Next
From: David Rowley
Date:
Subject: Re: Reducing the chunk header sizes on all memory context types