Re: Re: permissions on databases vs. permissions on tables

Currently I don't believe postgres has a way to prevent a user who can
connect to a database from creating objects in it. There's been talk
about the topic in the past (it's probably in one of the archives).
I'm not sure if anything was done on this front for 7.1.

On Thu, 9 Nov 2000, Ferruccio Zamuner wrote:

> Dear Jim,
>
> I've post the same question one week ago on pgsql-sql(at)postgresql(dot)org but
> none has answered until today.
> Perhaps this is not a problem or this seems an obvious topic.
>
> I hope that at least someone tells us how this question is silly.
>
>
> Bye, \fer
>
> > ok, so i know how to use GRANT/REVOKE to assign permission levels on tables.
>
> > however, it eludes me on how to do it on a database level.
>
> > i poked about in the manuals and nothing jumped out and said "here's how
> > you do it".
>
> > for example, i have a database called "samples".
>
> > in "samples", i have various tables which have been configured using
> > "GRANT/REVOKE" to allow/disallow various activities by users.
>
> > however, any user can create new tables.
>
> > how do i stop/restrict who can add tables (and/or indexes) ?