Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, maxim(dot)boguk(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view
Date: 2024-03-12 14:08:14
Message-ID: 1669466.1710252494@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> On Tue, 2024-03-12 at 01:02 +0200, Heikki Linnakangas wrote:
>> I guess we need to allow creating such internal temporary tables,
>> despite the missing permission. That'll need some careful analysis to
>> make sure we don't accidentally allow creating other temporary tables...

> Wouldn't it be sufficient to document that fact, perhaps add an
> error hint and require the MV owner to have TEMP on the database?

+1. I don't see a need for this to be a low-permissions feature.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message ocean_li_996 2024-03-12 15:07:22 Re:RE: Re:RE: Re:RE: Re:BUG #18369: logical decoding core on AssertTXNLsnOrder()
Previous Message Wetmore, Matthew (CTR) 2024-03-12 13:51:46 BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view