From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Greg Smith <greg(at)2ndquadrant(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, Josh Berkus <josh(at)agliodbs(dot)com>, "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Oleg Bartunov <obartunov(at)gmail(dot)com>, PgHacker <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [v9.4] row level security |
Date: | 2013-09-04 15:01:19 |
Message-ID: | 20130904150119.GD2706@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Robert Haas (robertmhaas(at)gmail(dot)com) wrote:
> On Sun, Sep 1, 2013 at 11:47 PM, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
> > And if someone can INSERT values that they can't actually see once they're
> > committed, that's a similarly bad we should describe.
>
> This is desirable in some cases but not others. If the goal is
> compartmentalization, then it's sensible to prevent this. But you
> might also have a "drop-box" environment - e.g. a student submits
> coursework to a professor, and can't access the submitted work after
> it's submitted. FWIW, my CS classes in college had a tool that worked
> just this way.
Agreed, and part of the discussion that I had w/ KaiGai and Simon was
that we should provide a way to let the user pick which they'd like.
This is the concept around 'insert privileges' being different from
'select privileges' wrt RLS.
> The point is that we should be in the business of providing mechanism,
> not policy.
++
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2013-09-04 15:01:30 | Re: 9.4 regression |
Previous Message | Andres Freund | 2013-09-04 15:00:55 | Re: [9.4] Make full_page_writes only settable on server start? |