Re: permissions on databases vs. permissions on tables - Mailing list pgsql-general

From Ferruccio Zamuner
Subject Re: permissions on databases vs. permissions on tables
Date
Msg-id 200011082343.eA8NhEW27005@tnt.diff.org
Whole thread Raw
In response to permissions on databases vs. permissions on tables  (Jim Mercer <jim@reptiles.org>)
Responses Re: Re: permissions on databases vs. permissions on tables  (Stephan Szabo <sszabo@megazone23.bigpanda.com>)
List pgsql-general
Dear Jim,

I've post the same question one week ago on pgsql-sql@postgresql.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) ?

> --
> [ Jim Mercer                 jim@reptiles.org              +1 416 410-5633 ]
> [          Reptilian Research -- Longer Life through Colder Blood          ]
> [  Don't be fooled by cheap Finnish imitations; BSD is the One True Code.  ]

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Relation 'pg_user' does not exist
Next
From: Matt Beauregard
Date:
Subject: Re: Relation 'pg_user' does not exist