Re: Feature: temporary materialized views
От | Tom Lane |
---|---|
Тема | Re: Feature: temporary materialized views |
Дата | |
Msg-id | 14550.1547740674@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Feature: temporary materialized views (Andreas Karlsson <andreas@proxel.se>) |
Ответы |
Re: Feature: temporary materialized views
|
Список | pgsql-hackers |
Andreas Karlsson <andreas@proxel.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
В списке pgsql-hackers по дате отправления: