| From: | Geoff Montee <geoff(dot)montee(at)gmail(dot)com> |
|---|---|
| To: | sumita <suday(at)avaya(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: security labels or sensitivity markings |
| Date: | 2014-07-14 08:42:38 |
| Message-ID: | CAA7biFMTqazGdVQFcKubuQQZ=PedQAaFWdTApFNpXTYvhQGVXw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Jul 14, 2014 at 2:23 AM, sumita <suday(at)avaya(dot)com> wrote:
> Does postgresql support the use of security labels or sensitivity
> markings?
>
>
>
If what you want is some kind of row-level security, you have to roll your
own when using PostgreSQL. Security_barrier views are a good option for
this. See:
http://blog.2ndquadrant.com/how-do-postgresql-security_barrier-views-work/
PostgreSQL 9.4 (out in a couple months) will be enhancing security_barrier
views, so they will also be updatable without requiring the use of triggers.
Geoff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc Mamin | 2014-07-14 11:32:23 | operator is not unique: smallint[] @> smallint[] You might need to add explicit type casts (!) |
| Previous Message | sumita | 2014-07-14 06:23:43 | security labels or sensitivity markings |