X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 01D2732A5A2 for ; Fri, 22 Oct 2004 14:33:58 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 20848-05 for ; Fri, 22 Oct 2004 13:33:49 +0000 (GMT) Received: from megazone.bigpanda.com (megazone.bigpanda.com [64.147.171.210]) by svr1.postgresql.org (Postfix) with ESMTP id B0BE6329E55 for ; Fri, 22 Oct 2004 14:33:56 +0100 (BST) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id BE35C35BD0; Fri, 22 Oct 2004 06:33:58 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id B5C6235BBE; Fri, 22 Oct 2004 06:33:58 -0700 (PDT) Date: Fri, 22 Oct 2004 06:33:58 -0700 (PDT) From: Stephan Szabo To: Joe Maldonado Cc: Scott Marlowe , pgsql-admin@postgresql.org Subject: Re: REVOKE not working... In-Reply-To: <41790751.2010803@webehosting.biz> Message-ID: <20041022063238.O1352@megazone.bigpanda.com> References: <41767366.7040305@webehosting.biz> <1098287120.21035.47.camel@localhost.localdomain> <4177E894.4060604@webehosting.biz> <1098389182.21035.72.camel@localhost.localdomain> <41790751.2010803@webehosting.biz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/305 X-Sequence-Number: 15298 On Fri, 22 Oct 2004, Joe Maldonado wrote: > Scott Marlowe wrote: > > >On Thu, 2004-10-21 at 10:49, Joe Maldonado wrote: > > > > > >>Scott Marlowe wrote: > >> > >> > >> > >>>On Wed, 2004-10-20 at 08:17, Joe Maldonado wrote: > >>> > >>> > >>> > >>> > >>>>Hello all, > >>>> I have created users for which I have restricted access to SELECT > >>>> > >>>> > >>>>from a set of tables, this works :) > >>> > >>> > >>>> But when I issue a REVOKE CREATE ON DATABASE mydb FROM myuser; > >>>>The user can still create tables...I've also issued this command for the > >>>>SCHEMA and still no go. > >>>> > >>>>Is this a known problem, if so how can I restrict users from creating > >>>>objects in my db? > >>>> > >>>> > >>>> > >>>> > >>>Is myuser a superuser? If so, you can revoke all you want and he'll > >>>still be able to do anything he wants. Also, I think that if myuser > >>>owns the current database he can always create tables in it. > >>> > >>> > >>> > >>> > >>> > >>> > >>myuser is not a superuser. is the public schema special in that you > >>cannot revoke create privileges from users accessing it? > >> > >> > > > >Is myuser the creator of the database in question? > > > > > >---------------------------(end of broadcast)--------------------------- > >TIP 6: Have you searched our list archives? > > > > http://archives.postgresql.org > > > > > Nope. I think Tom said this, but myuser probably doesn't have permission on the schema, it's probably getting the PUBLIC ("world") permission. You might need to revoke create on schema public from public; and then grant rights to users or groups that you want to give permissions to.