From: Tom Lane <tgl@sss.pgh.pa.us>
To: Laurenz Albe <laurenz.albe@cybertec.at>
cc: Heikki Linnakangas <hlinnaka@iki.fi>, maxim.boguk@gmail.com,
        pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18387: Erroneous permission checks and/or misleading error
 messages with refresh materialized view
In-reply-to: <ab150c8f181fd343d08ddf0896dc59496184db62.camel@cybertec.at>
References: <18387-12041858d9efb6f6@postgresql.org>
 <36bb333d-13ec-4f8e-af33-48249ca2fe69@iki.fi>
 <ab150c8f181fd343d08ddf0896dc59496184db62.camel@cybertec.at>
Comments: In-reply-to Laurenz Albe <laurenz.albe@cybertec.at>
	message dated "Tue, 12 Mar 2024 08:34:40 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1669465.1710252494.1@sss.pgh.pa.us>
Date: Tue, 12 Mar 2024 10:08:14 -0400
Message-ID: <1669466.1710252494@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1669466.1710252494%40sss.pgh.pa.us>
Precedence: bulk

Laurenz Albe <laurenz.albe@cybertec.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