Horton

Re: [v9.2] Fix Leaky View Problem

Robert Haas <robertmhaas@gmail.com>

View thread
From: Robert Haas <robertmhaas@gmail.com>
To: Kohei KaiGai <kaigai@kaigai.gr.jp>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Noah Misch <noah@leadboat.com>, Kevin Grittner <Kevin.Grittner@wicourts.gov>, Kohei.Kaigai@emea.nec.com, thom@linux.com, pgsql-hackers@postgresql.org
Date: 2011-10-21T14:47:46Z
Lists: pgsql-hackers 
On Fri, Oct 21, 2011 at 10:36 AM, Kohei KaiGai <kaigai@kaigai.gr.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