Re: Revoke for a new role
| От | Rafael Domiciano |
|---|---|
| Тема | Re: Revoke for a new role |
| Дата | |
| Msg-id | 3a0028490806130906i553f9588g810b2d19d95a91a1@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Revoke for a new role (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Revoke for a new role
|
| Список | pgsql-admin |
So, there is no manner to define that the user can't do create or drop objects, but can create temp tables?
I have to do it manually?
I have been reading about a patch that increment the CREATE ROLE clausule, called "PATCH NOCREATETABLE"...
This patch is what I need... someone had already hear some about?
I have to do it manually?
I have been reading about a patch that increment the CREATE ROLE clausule, called "PATCH NOCREATETABLE"...
This patch is what I need... someone had already hear some about?
2008/6/13 Tom Lane <tgl@sss.pgh.pa.us>:
"Milen A. Radev" <milen@radev.net> writes:
> Rafael Domiciano написа:>> I need to create a role (Postgres user) that cannot drop or create table,
>> but can create TEMP tables. This role must do I, U and D normally.> For a role to be able to create tables (and other objects) it shouldMore specifically, what you're going to need to do is revoke "public"
> have "CREATE" privilege on the _schema_ in question.
create access on the public schema, and then selectively grant it to
everyone you want to have it. There's no notion of "everyone but X
gets this privilege".
regards, tom lane
В списке pgsql-admin по дате отправления: