On Fri, Oct 21, 2011 at 10:36 AM, Kohei KaiGai <kai...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
