pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Stephen Frost <sfrost@snowman.net>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Greg Smith <greg@2ndquadrant.com>
Cc: Greg Stark <stark@mit.edu>
Cc: Kohei KaiGai <kaigai@kaigai.gr.jp>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: ktm@rice.edu <ktm@rice.edu>
Cc: Alexander Korotkov <aekorotkov@gmail.com>
Cc: Oleg Bartunov <obartunov@gmail.com>
Cc: PgHacker <pgsql-hackers@postgresql.org>
Subject: Re: [v9.4] row level security
Date: Wed, 4 Sep 2013 11:01:19 -0400
Message-ID: <20130904150119.GD2706@tamriel.snowman.net> (raw)
In-Reply-To: <CA+TgmoY4aAEft-jxbjpEw5O5E5DL-8NPqwtujgjvM-x+08TLtQ@mail.gmail.com>
References: <CADyhKSW_o2nVWFytdTY84DUXZSuZkD_EtY2d8wAjR18UruOXYQ@mail.gmail.com>
	<WM!fb94ecb91cd381e69d8e4773d3810f48e4e0ef000525cc806c4ee509f215ce1a39c8c2a1c3ffde72ba2ddb1a07ebcdc9!@asav-2.01.com>
	<5220D832.7090104@agliodbs.com>
	<CADyhKSWMvA-Ri7zD2gvz9bq2GiDLPQ_Hqmq86A5AL2r+em9+pw@mail.gmail.com>
	<WM!12ab40873dea1bdff46421b93993af10c7940c289ac32373a30649be9839739492ccb794e20a8b018ced351a2e740d55!@asav-3.01.com>
	<52238206.2060705@agliodbs.com>
	<CADyhKSXKdH2u4qa0Tgv3qUmfuHA9MprDOVfjCxRQyqP+UcC=kg@mail.gmail.com>
	<CAM-w4HOSTZh+gZxtJt+qbiFzwFQHXMiAqZJs2rxe53H+6Nn1RA@mail.gmail.com>
	<52240A43.3000100@2ndQuadrant.com>
	<CA+TgmoY4aAEft-jxbjpEw5O5E5DL-8NPqwtujgjvM-x+08TLtQ@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

* Robert Haas (robertmhaas@gmail.com) wrote:
> On Sun, Sep 1, 2013 at 11:47 PM, Greg Smith <greg@2ndquadrant.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

Attachments:

  [application/pgp-signature] signature.asc (197B, ../20130904150119.GD2706@tamriel.snowman.net/2-signature.asc)
  download

view thread (165+ messages)  latest in thread

Message-ID: <20130904150119.GD2706@tamriel.snowman.net>
Permalink:  ../20130904150119.GD2706@tamriel.snowman.net/
Also on:    postgresql.org/message-id/20130904150119.GD2706@tamriel.snowman.net

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: sfrost@snowman.net, robertmhaas@gmail.com, greg@2ndquadrant.com, stark@mit.edu, kaigai@kaigai.gr.jp, josh@agliodbs.com, ktm@rice.edu, aekorotkov@gmail.com, obartunov@gmail.com
  Subject: Re: [v9.4] row level security
  In-Reply-To: <20130904150119.GD2706@tamriel.snowman.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox