From: Nathan Bossart <nathandbossart@gmail.com>
To: Mark Dilger <mark.dilger@enterprisedb.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: predefined role(s) for VACUUM and ANALYZE
Date: Wed, 7 Sep 2022 15:21:29 -0700
Message-ID: <20220907222129.GB2095022@nathanxps13> (raw)
In-Reply-To: <6238B5AF-232A-4198-BB0F-0222675E7703@enterprisedb.com>
References: <20220722203735.GB3996698@nathanxps13>
<6238B5AF-232A-4198-BB0F-0222675E7703@enterprisedb.com>
On Wed, Sep 07, 2022 at 02:53:57PM -0700, Mark Dilger wrote:
> Assuming for the sake of argument that we should create a role something like you propose, can you explain why we should draw the line around just VACUUM and ANALYZE? I am not arguing for including these other commands, but don't want to regret having drawn the line in the wrong place when later we decide to add more roles like the one you are proposing.
There was some previous discussion around adding a pg_maintenance role that
could perform all of these commands [0]. I didn't intend to draw a line
around VACUUM and ANALYZE. Those are just the commands I started with.
If/when there are many of these roles, it might make sense to create a
pg_maintenance role that is a member of pg_vacuum_all_tables,
pg_analyze_all_tables, etc.
[0] https://postgr.es/m/67a1d667e8ec228b5e07f232184c80348c5d93f4.camel%40j-davis.com
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: nathandbossart@gmail.com, mark.dilger@enterprisedb.com
Subject: Re: predefined role(s) for VACUUM and ANALYZE
In-Reply-To: <20220907222129.GB2095022@nathanxps13>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox