| From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Predefined role pg_maintenance for VACUUM, ANALYZE, CHECKPOINT. |
| Date: | 2021-10-24 14:49:24 |
| Message-ID: | CALj2ACUgLvWoH-aqC5LkmwyTJsxXyXO3BO1_o6QDVifNzMRKTg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Oct 24, 2021 at 3:15 AM Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
>
> Add new predefined role pg_maintenance, which can issue VACUUM,
> ANALYZE, CHECKPOINT.
>
> Patch attached.
At this point, the idea of having a new role for maintenance work
looks good. With this patch and Mark Dilger's patch introducing a
bunch of new predefined roles, one concern is that we might reach to a
state where we will have patches being proposed for new predefined
roles for every database activity and the superuser eventually will
have nothing to do in the database, it just becomes dummy?
I'm not sure if Mark Dilger's patch on new predefined roles has a
suitable/same role that we can use here.
Are there any other database activities that fall under the
"maintenance" category? How about CLUSTER, REINDEX? I didn't check the
code for their permissions.
Regards,
Bharath Rupireddy.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2021-10-24 16:47:37 | Re: Predefined role pg_maintenance for VACUUM, ANALYZE, CHECKPOINT. |
| Previous Message | Andrew Dunstan | 2021-10-24 14:46:30 | Re: Postgres perl module namespace |