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 05:06:51 |
Message-ID: | 4AFCE96B.6010305@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
KaiGai Kohei wrote:
> In the v8.4 development cycle, I got a suggestion to reduce
> a burden of reviewer to split off a few functionalities, such
> as "security_context" system column and row-level access controls.
>
I lost track of this patch and related bits somewhere along the way, had
to triage my unread mail a few times. Could someone summarize how it now
fits into plans for more general row-level access controls in the
database? I know incompatibilities between the SEPosgreSQL model for row
filtering and thoughts for a more general permissions feature that did
something similar were a major design issue in the early 8.4 versions of
SEPostgreSQL, and that as you say you've been working on that. I'm not
sure what relationship there is between those two today though, or
exactly where the general non-SELinux row filtering is at on the roadmap.
--
Greg Smith 2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2009-11-13 05:19:43 | Re: write ahead logging in standby (streaming replication) |
Previous Message | Bruce Momjian | 2009-11-13 04:50:10 | Re: next CommitFest |