| From: | R D <mrk279(at)yahoo(dot)com> |
|---|---|
| To: | Michael Minock <mjm(at)cs(dot)umu(dot)se> |
| Cc: | pgsql-admin(at)postgreSQL(dot)org |
| Subject: | Re: Denying CREATE TABLE capability |
| Date: | 2001-03-13 07:40:17 |
| Message-ID: | 20010313074017.27403.qmail@web10002.mail.yahoo.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Unfortunately There is no way atleast i do not know of
such since you can not REVOKE this from users. I do
not know why The developers consider this as not so
inportant. This capability was in the todo list for
7.1 but was removed. I would like to see this feature
in postgres because I'm tyred dropping unnecessary
user tables. I'm also tired of hopeing to sse this and
atlast I'll migrate to another RDBMS :).
Rumen
--- Michael Minock <mjm(at)cs(dot)umu(dot)se> wrote:
> Hello all -
>
> My users are able to connect to a main database and
> then create their own
> databases.
> However I do not want them to be able to create
> tables in the main database.
> But in the main database, some users always create
> tables, which I have to
> periodically go in and drop.
>
> I have tried to deny users capability to add tables
> in the main database by
> revoking users rights on the catalog relations.
> Especially pg_class, etc... Still I have found no
> way to achieve the above
> policy.
>
> Does anyone know the trick to get this policy
> enforced?
>
> Thanks,
> Mike Minock
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://www.postgresql.org/search.mpl
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - Buy the things you want at great prices.
http://auctions.yahoo.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pgsql-admin | 2001-03-13 10:02:47 | Re: Use of the LIMIT clause ? |
| Previous Message | Karel Zak | 2001-03-13 06:44:16 | Re: Python, Postgres support? |