| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: predefined role(s) for VACUUM and ANALYZE |
| Date: | 2022-09-07 22:11:03 |
| Message-ID: | 20220907221103.GA2095022@nathanxps13 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 07, 2022 at 05:13:44PM -0400, Stephen Frost wrote:
> I disagree that we should put the onus for addressing this on the next
> person who wants to add bits and just willfully use up the last of them
> right now for what strikes me, at least, as a relatively marginal use
> case. If we had plenty of bits then, sure, let's use a couple of for
> this, but that isn't currently the case. If you want this feature then
> the onus is on you to do the legwork to make it such that we have plenty
> of bits.
FWIW what I really want is the new predefined roles. I received feedback
upthread that it might also make sense to give people more fine-grained
control, so I implemented that. And now you're telling me that I need to
redesign the ACL system. :)
I'm happy to give that project a try given there is agreement on the
direction and general interest in the patches. From the previous
discussion, it sounds like we want to first use a distinct set of bits for
each catalog table. Is that what I should proceed with?
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2022-09-07 22:21:29 | Re: predefined role(s) for VACUUM and ANALYZE |
| Previous Message | Mark Dilger | 2022-09-07 21:53:57 | Re: predefined role(s) for VACUUM and ANALYZE |