Ayush Vatsa <ayushvatsa1810@gmail.com> writes: > Thanks Robert for confirming, let me submit a patch to fix the same.
Well, the first thing you need is consensus on what the behavior should be instead.
I have a very vague recollection that we concluded that SELECT privilege was a reasonable check because if you have that you could manually prewarm by reading the table. That would lead to the conclusion that the minimal fix is to look at the owning table's privileges instead of the index's own privileges.
I feel like if you can blow up the cache by loading an entire table into memory with just select privilege on the table we should be ok with allowing the same person to name an index on the same table and load it into the cache too.
