Horton

Re: Clarification on Role Access Rights to Table Indexes

Nathan Bossart <nathandbossart@gmail.com>

View thread View on postgr.es
From: Nathan Bossart <nathandbossart@gmail.com>
To: Jeff Davis <pgsql@j-davis.com>
Cc: Corey Huinker <corey.huinker@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Ayush Vatsa <ayushvatsa1810@gmail.com>, Robert Haas <robertmhaas@gmail.com>, "David G. Johnston" <david.g.johnston@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2025-10-15T15:39:17Z
Lists: pgsql-hackers, pgsql-general 
On Tue, Oct 14, 2025 at 10:01:37AM -0700, Jeff Davis wrote:
> If we start with an OID, what's the right way to do these kinds of
> checks? Could we do an ACL check, then lock it, then do an ACL check
> again to catch OID wraparound?

I tried something like this upthread [0].  My feeling was that this was a
lot of complexity for not a lot of gain.  Perhaps it's still worth doing,
though.

[0] https://postgr.es/m/aOgmi6avE6qMw_6t%40nathan

-- 
nathan

Commits

  1. Fix privilege checks for pg_prewarm() on indexes.

  2. Fix lookup code for REINDEX INDEX.

  3. Fix redefinition of typedef RangeVar.

  4. Fix lookups in pg_{clear,restore}_{attribute,relation}_stats().

  5. dblink: Avoid locking relation before privilege check.