From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
---|---|
To: | KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH] SE-PgSQL/lite (r2429) |
Date: | 2009-11-13 06:19:42 |
Message-ID: | 4AFCFA7E.4040405@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
KaiGai Kohei wrote:
> I found a uncertain term in your comment.
> It seems to me the "model" has two meanings in this context.
> - The way to make access control decision (allowed? or denied?).
> - The granularity of access controls (tables? columns? or tuples?).
>
What I meant by "the SEPosgreSQL model for row filtering" was the
original implementation you had, where row filtering was handled by code
specific to SEPostgreSQL, not something generic enough to be used for
other purposes. I wasn't sure what if anything from there was still in
the patch, and you answered that clearly enough. Thanks for clarifying
where things are at.
--
Greg Smith 2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-11-13 06:25:26 | Re: CTE containing ambiguous columns |
Previous Message | Greg Smith | 2009-11-13 06:17:48 | Re: write ahead logging in standby (streaming replication) |