From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | Carlos Mennens <carlos(dot)mennens(at)gmail(dot)com> |
Subject: | Re: Role Membership |
Date: | 2010-12-20 20:20:23 |
Message-ID: | 201012201220.24091.adrian.klaver@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Monday 20 December 2010 11:46:29 am Carlos Mennens wrote:
> On Mon, Dec 20, 2010 at 1:32 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
wrote:
> > No user, no group, they're al roles. Roles are both / either.
>
> Ah now I understand. Thank you!
>
> > You grant them that:
> >
> > grant rolename to username;
> >
> > Then you only ever have to grant / revoke a role to change
> > permissions, no need to do a million grants all over the place on each
> > table. Just grant it once to the role, grant the role to the user,
> > viola, you're done.
>
> OK I now understand:
>
Now I don't:) What you show is changing the ownership of an object. I thought
you where asking about how to add members to a role and the relationship
between 'users' and 'groups'? What Scott showed was a good start, but I would
suggest some more experimenting. ROLES are powerful but there is a learning
curve, especially when you start using SET ROLE and SET SESSION AUTHORIZATION.
> Thanks for helping me out!
>
> -Carlos
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2010-12-20 20:31:23 | Re: PostgreSQL Trusted Startup |
Previous Message | Carlos Mennens | 2010-12-20 19:46:29 | Re: Role Membership |