mirror of
https://github.com/postgres/postgres.git
synced 2025-07-08 11:42:09 +03:00
Revert MAINTAIN privilege and pg_maintain predefined role.
This reverts the following commits:4dbdb82513
,c2122aae63
,5b1a879943
,9e1e9d6560
,ff9618e82a
,60684dd834
,4441fc704d
, andb5d6382496
. A role with the MAINTAIN privilege may be able to use search_path tricks to escalate privileges to the table owner. Unfortunately, it is too late in the v16 development cycle to apply the proposed fix, i.e., restricting search_path when running maintenance commands. Bumps catversion. Reviewed-by: Jeff Davis Discussion: https://postgr.es/m/E1q7j7Y-000z1H-Hr%40gemulon.postgresql.org Backpatch-through: 16
This commit is contained in:
@ -159,15 +159,16 @@ analyze_rel(Oid relid, RangeVar *relation,
|
||||
return;
|
||||
|
||||
/*
|
||||
* Check if relation needs to be skipped based on privileges. This check
|
||||
* Check if relation needs to be skipped based on ownership. 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 privileges could have changed
|
||||
* in-between. Make sure to generate only logs for ANALYZE in this case.
|
||||
* happen across multiple transactions where relation ownership could have
|
||||
* changed in-between. Make sure to generate only logs for ANALYZE in
|
||||
* this case.
|
||||
*/
|
||||
if (!vacuum_is_permitted_for_relation(RelationGetRelid(onerel),
|
||||
onerel->rd_rel,
|
||||
params->options & ~VACOPT_VACUUM))
|
||||
if (!vacuum_is_relation_owner(RelationGetRelid(onerel),
|
||||
onerel->rd_rel,
|
||||
params->options & VACOPT_ANALYZE))
|
||||
{
|
||||
relation_close(onerel, ShareUpdateExclusiveLock);
|
||||
return;
|
||||
|
Reference in New Issue
Block a user