Re: Clarification on Role Access Rights to Table Indexes

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ayush Vatsa <ayushvatsa1810(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Clarification on Role Access Rights to Table Indexes
Date: 2025-10-15 15:39:17
Message-ID: aO_AJd3Au9xmSwjD@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Nathan Bossart 2025-10-15 17:54:21 Re: Clarification on Role Access Rights to Table Indexes
Previous Message Dominique Devienne 2025-10-15 09:51:32 Re: Option on `postgres` CLI to shutdown when there are no more active connections?

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2025-10-15 15:46:28 Re: Thoughts on a "global" client configuration?
Previous Message Joel Jacobson 2025-10-15 15:36:11 Re: Optimize LISTEN/NOTIFY