| From: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Carol Cheung <cacheung(at)consumercontact(dot)com>, pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: meaning of "create role" |
| Date: | 2007-06-20 17:02:35 |
| Message-ID: | 3651474E-01A6-4FB2-B613-F1BB18B7E347@seespotcode.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On Jun 20, 2007, at 10:34 , Tom Lane wrote:
> Michael Glaesemann <grzm(at)seespotcode(dot)net> writes:
>> For the roles (users) on your system, yes. Though you should have at
>> least one superuser who has CREATEROLE, otherwise you couldn't create
>> new roles.
>
> A user with the superuser flag set can do anything; the states of the
> other flags are meaningless for him.
Yes, that was poorly worded. What I was trying to get at was that
there should be a superuser on the system who would be able to create
additional roles.
Michael Glaesemann
grzm seespotcode net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anastasios Hatzis | 2007-06-20 17:57:58 | Re: On managerial choosing (was: Postgres VS Oracle) |
| Previous Message | nhrcommu | 2007-06-20 16:05:05 | Re: Simple, Add constraint |