Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 45E1F9FB558 for ; Fri, 27 Jul 2007 06:03:59 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 08410-08 for ; Fri, 27 Jul 2007 06:03:52 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id B62309FB272 for ; Fri, 27 Jul 2007 06:03:55 -0300 (ADT) Received: from alvh.no-ip.org ([64.122.184.54]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l6R93rQv020709; Fri, 27 Jul 2007 02:03:53 -0700 Received: by alvh.no-ip.org (Postfix, from userid 1000) id 2CCFC4381D9; Fri, 27 Jul 2007 02:03:53 -0700 (PDT) Date: Fri, 27 Jul 2007 05:03:53 -0400 From: Alvaro Herrera To: Anderson Alves de Albuquerque Cc: pgsql-admin@postgresql.org Subject: Re: No create table Message-ID: <20070727090353.GG2550@alvh.no-ip.org> Mail-Followup-To: Anderson Alves de Albuquerque , pgsql-admin@postgresql.org References: <9b3f75f0707260856u66b37b91w5a842f6d0b6dc6ec@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9b3f75f0707260856u66b37b91w5a842f6d0b6dc6ec@mail.gmail.com> User-Agent: Mutt/1.5.16 (2007-06-11) X-Virus-Scanned: ClamAV 0.90.3/3775/Wed Jul 25 22:56:02 2007 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Fri, 27 Jul 2007 02:03:53 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/305 X-Sequence-Number: 26286 Anderson Alves de Albuquerque wrote: > I need to use a user that can not have permission to create table in one > BD. > > I use revoke, I tray with "revoke all on database XXX to|from USERNAME;", > but I don't have success. > > Could someone help me? You have to revoke permissions from the _schema_, not from databases. Say, revoke all on schema PUBLIC FROM PUBLIC; revoke all on schema PUBLIC FROM username; You have to remove from PUBLIC because otherwise the user will still have permissions to create via that privilege, even if you take his own permission away (if he had one at all actually). -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support