From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andreas Karlsson <andreas(at)proxel(dot)se> |
Cc: | Mitar <mmitar(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Feature: temporary materialized views |
Date: | 2019-01-17 15:57:54 |
Message-ID: | 14550.1547740674@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andreas Karlsson <andreas(at)proxel(dot)se> writes:
> On 1/11/19 8:47 PM, Mitar wrote:
>>> Is it really ok to just remove SECURITY_RESTRICTED_OPERATION from
>>> ExecCreateTableAs()?
>> The comment there said that this is not really necessary for security:
>> "This is not necessary for security, but this keeps the behavior
>> similar to REFRESH MATERIALIZED VIEW. Otherwise, one could create a
>> materialized view not possible to refresh."
> Hm, I am still not convinced just removing it is a good idea. Sure, it
> is not a security issue but usability is also important.
Indeed. I don't buy the argument that this should work differently
for temp views. The fact that they're only accessible in the current
session is no excuse for that: security considerations still matter,
because you can have different privilege contexts within a single
session (consider SECURITY DEFINER functions etc).
What is the stumbling block to just leaving that alone?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | James Coleman | 2019-01-17 15:58:10 | Re: Proving IS NOT NULL inference for ScalarArrayOpExpr's |
Previous Message | Tom Lane | 2019-01-17 15:52:19 | Re: Early WIP/PoC for inlining CTEs |