Re: Predefined role pg_maintenance for VACUUM, ANALYZE, CHECKPOINT.

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Vik Fearing <vik(at)postgresfriends(dot)org>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Predefined role pg_maintenance for VACUUM, ANALYZE, CHECKPOINT.
Date: 2021-11-02 22:30:25
Message-ID: CAKFQuwZkNHUpsR+oTCc3hfmnVWtY8cxXKOkniKrfKogqkSjWdA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 2, 2021 at 3:14 PM Vik Fearing <vik(at)postgresfriends(dot)org> wrote:

> On 11/2/21 4:06 PM, Robert Haas wrote:
> > There's bound to be somebody who wants to grant some of
> > these permissions and not others, or who wants to grant the ability to
> > run those commands on some tables but not others.
> Is there anything stopping us from adding syntax like this?
>
> GRANT VACUUM, ANALYZE ON TABLE foo TO bar;
>
> That doesn't fix the CHECKPOINT issue, but surely vacuum and analyze can
> be done that way. I would much prefer that over new predefined roles.
>
> This would be nice, but there is nothing to hang our hat on:
>
> GRANT CHECKPOINT TO username;
>
>
Here is the thread when I last brought up this idea five years ago:

https://www.postgresql.org/message-id/CAKFQuwaAhVt6audf92Q1VrELfJ%2BPz%3DuDfNb8%3D1_bqAmyDpnDmA%40mail.gmail.com

I do not believe we've actually consumed any of the then available
permission bits in the meanwhile.

David J.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2021-11-02 22:33:40 AArch64 has single-copy 64 bit atomicity
Previous Message Vik Fearing 2021-11-02 22:14:20 Re: Predefined role pg_maintenance for VACUUM, ANALYZE, CHECKPOINT.