Re: un-revert the MAINTAIN privilege and the pg_maintain predefined role

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: un-revert the MAINTAIN privilege and the pg_maintain predefined role
Date: 2024-03-13 16:49:26
Message-ID: 031d60d1dcb869da4effe5e56411f8bdd01dd3a0.camel@j-davis.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 2024-03-12 at 16:05 -0500, Nathan Bossart wrote:
> It's easy enough to resolve this inconsistency by sending
> down the parent OID when recursing to a TOAST table and using that
> for the
> privilege checks.  AFAICT this avoids any kind of cache lookup
> hazards
> because we hold a session lock on the main relation in this case. 
> I've
> done this in the attached v2.

Looks good to me. Thank you for expanding on the comment, as well.

Regards,
Jeff Davis

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Lakhin 2024-03-13 17:00:00 Re: pg16: XX000: could not find pathkey item to sort
Previous Message Bharath Rupireddy 2024-03-13 16:46:13 Re: Introduce XID age and inactive timeout based replication slot invalidation