| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Noah Misch <noah(at)leadboat(dot)com>, Kevin Grittner <kgrittn(at)ymail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: sepgsql and materialized views |
| Date: | 2015-03-10 01:16:37 |
| Message-ID: | 20150310011637.GO29780@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Alvaro Herrera (alvherre(at)2ndquadrant(dot)com) wrote:
> Kohei KaiGai wrote:
> > Unfortunately, I could not get consensus of design on selinux policy side.
> > Even though my opinion is to add individual security class for materialized
> > view to implement refresh permission, other people has different opinion.
> > So, I don't want it shall be a blocker of v9.3 to avoid waste of time.
> > Also, I'll remind selinux community on this issue again, and tries to handle
> > in another way from what I proposed before.
>
> Did we get this fixed?
I don't think so, but it's something I'm interested in and have an
envrionment where I can work on it.
Will look into it and try to provide an update soon.
Any further thoughts or suggestions would be appreciated.
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Haribabu Kommi | 2015-03-10 01:20:36 | Re: Parallel Seq Scan |
| Previous Message | Michael Paquier | 2015-03-10 00:57:50 | Re: New functions |