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

From Andrew Dunstan
Subject Re: pre-proposal: permissions made easier
Date
Msg-id 4A48F972.70800@dunslane.net
Whole thread Raw
In response to Re: pre-proposal: permissions made easier  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers

Jeff Davis wrote:
> On Mon, 2009-06-29 at 12:55 -0400, Tom Lane wrote:
>   
>> I think it has to be looked at in comparison to more general
>> prospective-permissions schemes; 
>>     
>
> When I searched google for "prospective permissions", all I found were
> links to messages in this thread ;)
>
> Can you refer me to a general prospective-permissions scheme that is
> more widely accepted? Being more widely accepted also has the benefit
> that users will feel more comfortable with the behavior.
>
>
>   

Think of MySQL's wildcard permissions. They apply to any object whether 
that object is created before or after the rule is set, AIUI. That means 
the wildcard pattern is applied at the time the permission rule is 
referenced, rather than when the rule is created, thus applying it 
prospectively.

It's a feature many users would like to have, although, as Tom rightly 
points out, it can be a bit of a footgun if used carelessly.

cheers

andrew


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_restore -t table concerns
Next
From: Andrew Dunstan
Date:
Subject: Re: pg_restore -t table concerns