| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
| Cc: | Bruno Wolff III <bruno(at)wolff(dot)to>, William ZHANG <uniware(at)zedware(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: CREATE USER and pg_user |
| Date: | 2005-08-22 20:17:49 |
| Message-ID: | 20865.1124741869@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Jim C. Nasby" <jnasby(at)pervasive(dot)com> writes:
> On Fri, Aug 12, 2005 at 08:55:09AM -0500, Bruno Wolff III wrote:
>> For more information take a look at the CREATE ROLE command in the
>> developer docs.
> ISTM that it's a bug to be able to assign permissions that you don't
> yourself have. In this case, if you have CREATEROLE but not SUPERUSER,
> then you should be able to create roles, but not ones that have
> SUPERUSER status. If this isn't how it currently works then there should
> be a big warning under CREATEROLE.
Did you read the docs Bruno pointed you to?
http://developer.postgresql.org/docs/postgres/sql-createrole.html
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rosser Schwarz | 2005-08-22 20:24:00 | beginning hackers (was: indexes spanning multiple tables) |
| Previous Message | Hannu Krosing | 2005-08-22 20:17:23 | Re: Missing CONCURRENT VACUUM (Was: Release notes for |