Re: Review of Row Level Security - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: Review of Row Level Security
Date
Msg-id 20121220194213.GI12354@tamriel.snowman.net
Whole thread Raw
In response to Re: Review of Row Level Security  ("Kevin Grittner" <kgrittn@mail.com>)
Responses Re: Review of Row Level Security  (Kohei KaiGai <kaigai@kaigai.gr.jp>)
Re: Review of Row Level Security  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Kevin, all,

* Kevin Grittner (kgrittn@mail.com) wrote:
> The more secure behavior is to allow entry of data which will not
> be visible by the person doing the entry.

wrt this- I'm inclined to agree with Kevin.  It's certainly common in
certain environments that you can write to a higher level than you can
read from.  Granting those writers access to read the data later would
be... difficult.

What we're really arguing about here, afaict, is what the default should
be.  In line with Kevin's comments and Tom's reading of the spec (along
with my own experience in these environments), I'd argue for the default
to allow writing rows you're not allowed to read.

It would certainly be ideal if we could support both options, on a
per-relation basis, when we release the overall feature.  It doesn't
"feel" like it'd be a lot of work to do that, but I've not been able to
follow this discussion up til now.  Thankfully, I'm hopeful that I'm
going to have more time now to keep up with PG. :)
Thanks,
    Stephen

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Feature Request: pg_replication_master()
Next
From: Robert Haas
Date:
Subject: Re: Review of Row Level Security