| From: | Mitar <mmitar(at)gmail(dot)com> |
|---|---|
| To: | Andreas Karlsson <andreas(at)proxel(dot)se> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-18 01:50:32 |
| Message-ID: | CAKLmikO9WY5Rf3NG=nGicq4mm_up6EymMrbU5CiR+YNaP0voWw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi!
On Thu, Jan 17, 2019 at 9:53 AM Andreas Karlsson <andreas(at)proxel(dot)se> wrote:
> > What is the stumbling block to just leaving that alone?
>
> I think the issue Mitar ran into is that the temporary materialized view
> is created in the rStartup callback of the receiver which happens after
> SECURITY_RESTRICTED_OPERATION is set in ExecCreateTableAs(), so the
> creation of the view itself is denied.
Yes, the error without that change is:
ERROR: cannot create temporary table within security-restricted operation
Mitar
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mitar | 2019-01-18 01:53:08 | Re: Feature: temporary materialized views |
| Previous Message | Haribabu Kommi | 2019-01-18 01:37:48 | Re: [HACKERS] Block level parallel vacuum |