Re: pre-proposal: permissions made easier - Mailing list pgsql-hackers

From Greg Stark
Subject Re: pre-proposal: permissions made easier
Date
Msg-id 407d949e0906291253h2a429d66p14cfd6330da37c10@mail.gmail.com
Whole thread Raw
In response to Re: pre-proposal: permissions made easier  (Josh Berkus <josh@agliodbs.com>)
Responses Re: pre-proposal: permissions made easier  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
On Mon, Jun 29, 2009 at 7:41 PM, Josh Berkus<josh@agliodbs.com> wrote:
> The main reason is existing practice.

I haven't followed the entire conversation so i'm not sure who I'm
going to be disagreeing with or agreeing with here. But I wanted to
mention that existing practice may not be a very useful place to start
here. Whatever mechanism we invent is going to change the calculus of
people deciding how to set up their schemas and roles since they'll
want to arrange things to take advantage of this new mechanism.

In particular, one early question was whether to use wildcard patterns
or schema names. People were saying wildcard patterns would be more
flexible because people don't always set up their objects in different
schemas. But if we had a mechanism someone wanted to use which
depended on schemas they would be far more likely to choose to set up
schemas for objects which belong in different security classes.

-- 
greg
http://mit.edu/~gsstark/resume.pdf


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: pre-proposal: permissions made easier
Next
From: Josh Berkus
Date:
Subject: Re: pre-proposal: permissions made easier