Date: Wed, 15 Oct 2025 10:39:17 -0500
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>
Subject: Re: Clarification on Role Access Rights to Table Indexes
Message-ID: <aO_AJd3Au9xmSwjD@nathan>
References: <8af53c6e8992aa706e63aafe60a3bcf100b524d1.camel@j-davis.com>
 <7b0e2774cdcc8f522ac82f64a8d7266f353a5094.camel@j-davis.com>
 <aOfXNAFkj_EFm-8q@nathan>
 <aOgmi6avE6qMw_6t@nathan>
 <aOkzoH-pXdBr0ewf@nathan>
 <31a67adbb10b85ff7cddeafe75b9f6505c902e57.camel@j-davis.com>
 <aO1TaPd0YesHy5Sn@nathan>
 <bd0826223bff21bd2ad3d0b1520ee8429568c526.camel@j-davis.com>
 <aO50zOmoRFnB9_IX@nathan>
 <857a4633aea6ef90bde4156ae351c49794b34732.camel@j-davis.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <857a4633aea6ef90bde4156ae351c49794b34732.camel@j-davis.com>
Archived-At: <https://www.postgresql.org/message-id/aO_AJd3Au9xmSwjD%40nathan>
Precedence: bulk

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