mirror of
https://github.com/postgres/postgres.git
synced 2025-09-11 00:12:06 +03:00
Reintroduce MAINTAIN privilege and pg_maintain predefined role.
Roles with MAINTAIN on a relation may run VACUUM, ANALYZE, REINDEX, REFRESH MATERIALIZE VIEW, CLUSTER, and LOCK TABLE on the relation. Roles with privileges of pg_maintain may run those same commands on all relations. This was previously committed for v16, but it was reverted in commit151c22deee
due to concerns about search_path tricks that could be used to escalate privileges to the table owner. Commits2af07e2f74
,59825d1639
, andc7ea3f4229
resolved these concerns by restricting search_path when running maintenance commands. Bumps catversion. Reviewed-by: Jeff Davis Discussion: https://postgr.es/m/20240305161235.GA3478007%40nathanxps13
This commit is contained in:
@@ -149,16 +149,15 @@ analyze_rel(Oid relid, RangeVar *relation,
|
||||
return;
|
||||
|
||||
/*
|
||||
* Check if relation needs to be skipped based on ownership. This check
|
||||
* Check if relation needs to be skipped based on privileges. This check
|
||||
* happens also when building the relation list to analyze for a manual
|
||||
* operation, and needs to be done additionally here as ANALYZE could
|
||||
* happen across multiple transactions where relation ownership could have
|
||||
* changed in-between. Make sure to generate only logs for ANALYZE in
|
||||
* this case.
|
||||
* happen across multiple transactions where privileges could have changed
|
||||
* in-between. Make sure to generate only logs for ANALYZE in this case.
|
||||
*/
|
||||
if (!vacuum_is_relation_owner(RelationGetRelid(onerel),
|
||||
onerel->rd_rel,
|
||||
params->options & VACOPT_ANALYZE))
|
||||
if (!vacuum_is_permitted_for_relation(RelationGetRelid(onerel),
|
||||
onerel->rd_rel,
|
||||
params->options & ~VACOPT_VACUUM))
|
||||
{
|
||||
relation_close(onerel, ShareUpdateExclusiveLock);
|
||||
return;
|
||||
|
Reference in New Issue
Block a user