| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Noah Misch <noah(at)leadboat(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Kohei(dot)Kaigai(at)emea(dot)nec(dot)com, thom(at)linux(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [v9.2] Fix Leaky View Problem |
| Date: | 2011-10-21 14:47:46 |
| Message-ID: | CA+TgmobByPeWuDHvQ-4n7eCnB4gQ91wZu6bsz=iumrLut2e2=Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 21, 2011 at 10:36 AM, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> wrote:
> So, I will split the patch into two parts as follows, in the next commit fest.
>
> Part-1) Views with security_barrier reloption
>
> The part-1 portion provides views "security_barrier" reloption; that enables
> to keep sub-queries unflatten in the prepjoin.c stage.
> In addition, these sub-queries (that originally come from views with
> "security_barrier" option) don't allow to push down qualifiers from upper
> level. It shall prevent both of the problematic scenarios.
>
> Part-2) Functions with leakproof attribute
>
> The part-2 portion provides functions "leakproof" attribute; that enables
> to push down leakproof functions into sub-queries, even if it originally
> come from security views.
> It shall minimize performance damages when we use view for row-level
> security purpose.
Sounds reasonable.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kohei KaiGai | 2011-10-21 14:53:33 | Re: WIP: Join push-down for foreign tables |
| Previous Message | Robert Haas | 2011-10-21 14:46:30 | Re: pg_upgrade if 'postgres' database is dropped |