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 3ED6652ABE for ; Wed, 13 Jul 2005 13:49:18 -0300 (ADT) 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 94047-03 for ; Wed, 13 Jul 2005 16:49:15 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id AB6E352A1A for ; Wed, 13 Jul 2005 13:49:13 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j6DGnBUU009314; Wed, 13 Jul 2005 12:49:11 -0400 (EDT) To: Chris Hoover Cc: pgsql-admin@postgresql.org Subject: Re: 7.3 and user permissions In-reply-to: <1d219a6f05071308424e3d4199@mail.gmail.com> References: <1d219a6f05071308424e3d4199@mail.gmail.com> Comments: In-reply-to Chris Hoover message dated "Wed, 13 Jul 2005 11:42:48 -0400" Date: Wed, 13 Jul 2005 12:49:11 -0400 Message-ID: <9313.1121273351@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200507/84 X-Sequence-Number: 18140 Chris Hoover writes: > I'm having a strange issue. I just created a new user with createdb > and createuser permissions. The user only has permissions to view the > data in one database. However, when I login to any db as him, I am > able to select data from tables that he has no select permisisons on. "createuser" actually means "superuser" ... does that make it clearer? PG 8.1 will have a privilege level that allows creation of users without full superuserdom, but no existing release does. > Also, I would really prefer that this user only have access to his one > db and not able to see anything in the other db's. Is this possible? Database connection privileges are controlled by pg_hba.conf; you could adjust that file to allow this user access to only his own database. Better take away his superuser rights first though, else he could undo the change if he chose to. regards, tom lane