| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, David Fetter <david(at)fetter(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pre-proposal: permissions made easier |
| Date: | 2009-06-29 19:42:50 |
| Message-ID: | 4A49193A.7010305@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom,
> From what I recall of prior discussions, there is rough consensus that
> the two types of facilities you mentioned (setting up default ACLs to be
> applied at creation of objects created later, and providing a way to
> change multiple objects' permissions with one GRANT) are desirable,
> though there is plenty of argument about the details. Neither of these
> result in creating any new sources of permissions --- a given object's
> ACL is still the whole truth.
yeah, that's why I've been working on that approach. It doesn't
simplify things as much as some DBAs might want, but it's the most
side-effect-free approach.
--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2009-06-29 19:53:54 | Re: pre-proposal: permissions made easier |
| Previous Message | Ms swati chande | 2009-06-29 19:32:31 | facing problem with createdb. |