| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Skip ExecCheckRTPerms in CTAS with no data |
| Date: | 2020-11-20 07:29:19 |
| Message-ID: | d4cf6e11-e489-bb82-e1f6-67504bbc162d@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-11-20 06:37, Michael Paquier wrote:
>>> But if you consider materialized views as a variant of normal views,
>>> then the INSERT privilege would be applicable if you pass an INSERT on
>>> the materialized view through to the underlying tables, like for a view.
> INSERT to materialized views is not supported, but perhaps you mean
> having a variant of auto updatable for matviews? I am not sure how to
> clearly define that.
Not currently, but it could be a future feature. Basically an insert
would be passed on to the underlying tables (using INSTEAD triggers),
and then a refresh would be triggered automatically.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2020-11-20 07:29:35 | Re: Protect syscache from bloating with negative cache entries |
| Previous Message | Michael Paquier | 2020-11-20 07:28:01 | Re: Online verification of checksums |