|From:||Stephen Frost <sfrost(at)snowman(dot)net>|
|To:||Jeff Davis <pgsql(at)j-davis(dot)com>|
|Cc:||Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, "Bossart, Nathan" <bossartn(at)amazon(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: Predefined role pg_maintenance for VACUUM, ANALYZE, CHECKPOINT.|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
* Jeff Davis (pgsql(at)j-davis(dot)com) wrote:
> On Mon, 2021-11-08 at 12:47 -0500, Stephen Frost wrote:
> > I don't feel as strongly as others apparently do on this point
> > though,
> > and I'd rather have non-superusers able to run CHECKPOINT *somehow*
> > than not, so if the others feel like a predefined role is a better
> > approach then I'm alright with that. Seems a bit overkill to me but
> > it's also not like it's actually all that much code or work to do.
> +1. It seems like the pg_checkpointer predefined role is the most
> acceptable to everyone (even if not universally liked).
> Attached a rebased version of that patch.
Thanks. Quick review-
> diff --git a/src/backend/tcop/utility.c b/src/backend/tcop/utility.c
> index bf085aa93b2..0ff832a62c2 100644
> --- a/src/backend/tcop/utility.c
> +++ b/src/backend/tcop/utility.c
> @@ -24,6 +24,7 @@
> #include "catalog/catalog.h"
> #include "catalog/index.h"
> #include "catalog/namespace.h"
> +#include "catalog/pg_authid.h"
> #include "catalog/pg_inherits.h"
> #include "catalog/toasting.h"
> #include "commands/alter.h"
> @@ -939,10 +940,10 @@ standard_ProcessUtility(PlannedStmt *pstmt,
> case T_CheckPointStmt:
> - if (!superuser())
> + if (!has_privs_of_role(GetUserId(), ROLE_PG_CHECKPOINTER))
> - errmsg("must be superuser to do CHECKPOINT")));
> + errmsg("must be member of pg_checkpointer to do CHECKPOINT")));
Most such error messages say 'superuser or '... Also, note the recent
thread about trying to ensure that places are using has_privs_of_role()
as you're doing here but also say that in the error message
consistently, rather than 'member of' it should really be 'has
privileges of' as the two are not necessarily always the same. You can
be a member of a role but not actively have the privileges of that role.
Otherwise, looks pretty good to me. I'll note that has_privs_of_role()
will first call superuser_arg(member), just the same as the prior
superuser() check did, so this doesn't change the catalog accesses in
that case from today.
|Next Message||Mark Dilger||2021-11-09 16:32:22||Re: CREATE ROLE IF NOT EXISTS|
|Previous Message||David Christensen||2021-11-09 16:28:14||Re: CREATE ROLE IF NOT EXISTS|