On Fri, Dec 09, 2022 at 10:40:55AM -0800, Nathan Bossart wrote: > On Fri, Dec 09, 2022 at 01:36:03PM +0900, Michael Paquier wrote: >> On Thu, Dec 08, 2022 at 09:15:03AM -0800, Nathan Bossart wrote: >>> The main idea behind this work is breaking out privileges into more >>> granular pieces. If I want to create a role that only runs VACUUM on some >>> tables on the weekend, why Ń•hould I have to also give it the ability to >>> ANALYZE, REFRESH, CLUSTER, and REINDEX? IMHO we should really let the user >>> decide what set of privileges makes sense for their use-case. I'm unsure >>> the grouping all these privileges together serves much purpose besides >>> preserving ACL bits. >> >> Hmm. I'd like to think that we should keep a frugal mind here. More >> bits are now available, but it does not strike me as a good idea to >> force their usage more than necessary, so grouping all these no-quite >> DDL commands into the same bag does not sound that bad to me. > > Okay, it seems I am outnumbered. I will work on updating the patch to add > an ACL_MAINTAIN bit and a pg_maintain_all_tables predefined role.
Any thoughts on $SUBJECT? -- Nathan Bossart Amazon Web Services: https://aws.amazon.com
