Re: Revoke for a new role - Mailing list pgsql-admin

From Rafael Domiciano
Subject Re: Revoke for a new role
Date
Msg-id 3a0028490806130906i553f9588g810b2d19d95a91a1@mail.gmail.com
Whole thread Raw
In response to Re: Revoke for a new role  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Revoke for a new role  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List 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?

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 should
> have "CREATE" privilege on the _schema_ in question.

More specifically, what you're going to need to do is revoke "public"
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 by date:

Previous
From: Tom Lane
Date:
Subject: Re: Revoke for a new role
Next
From: NOW Web Sites Manager
Date:
Subject: block error, but can't pg_dump