Re: [PATCHES] Users/Groups -> Roles

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] Users/Groups -> Roles
Date: 2005-07-01 20:57:18
Message-ID: 6573.1120251438@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> writes:
>> Right, this can be done now.

> There is the namespace collision issue, and although I might grant a
> student the privilege to create simple roles, I would not allow them to
> create new users for a basic practice;-)

Why not? With the setup Stephen suggests, they could create only new
users that could only get into their own database (since they'd not be
able to grant connect rights to other databases).

We probably need to think a bit harder about the meaning of CREATEROLE
though. Right now it gives free license not only to create roles but
to alter any property of existing roles. This seems appropriate if you
think of it as a "safer form of superuser", which is how I was thinking
of it. It would be too powerful for Fabien's situation though.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Larry Rosenman 2005-07-01 21:19:49 HEAD: create index failure: firefly on buildfarm
Previous Message Tom Lane 2005-07-01 20:29:27 Re: Regression test plpgsql vs. rangefuncs conflict

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2005-07-01 21:06:19 Use of E'' in pg_dump
Previous Message Heikki Linnakangas 2005-07-01 20:26:33 Re: psql tab-completion for COMMIT/ROLLBACK PREPARED