Re: Clarification on Role Access Rights to Table Indexes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Ayush Vatsa <ayushvatsa1810(at)gmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Clarification on Role Access Rights to Table Indexes
Date: 2025-02-17 19:13:09
Message-ID: 861660.1739819589@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Monday, February 17, 2025, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> You'd really have to take that up with the author of pg_prewarm.

> This is our contrib module so this seems like the expected place to ask
> such a question. It’s neither a bug nor a topic for -hackers. FTR, Robert
> Haas is the author from 2013. Not sure he monitors -general though.

Ah, you are right, I was thinking it was a third-party extension.

If we're talking about changing the behavior of a contrib module,
I think -hackers would be the appropriate location for that.
And it does seem like this deserves a fresh look. As it stands,
a superuser can prewarm an index (because she bypasses all
privilege checks including this one), but nobody else can.
Seems weird.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ayush Vatsa 2025-02-17 19:42:44 Re: Clarification on Role Access Rights to Table Indexes
Previous Message David G. Johnston 2025-02-17 18:43:04 Re: Clarification on Role Access Rights to Table Indexes

Browse pgsql-hackers by date

  From Date Subject
Next Message Sergey Belyashov 2025-02-17 19:17:05 Re: BUG #18815: Logical replication worker Segmentation fault
Previous Message Daniel Gustafsson 2025-02-17 19:03:39 Re: New buildfarm animals with FIPS mode enabled