Re: Restricting login to a single database only (no visible table spaces, groups or roles)
От | Guillaume Lelarge |
---|---|
Тема | Re: Restricting login to a single database only (no visible table spaces, groups or roles) |
Дата | |
Msg-id | 4BEB1ABB.6090500@lelarge.info обсуждение исходный текст |
Ответ на | Restricting login to a single database only (no visible table spaces, groups or roles) (Bryce Nesbitt <bnesbitt@bepress.com>) |
Ответы |
Re: Restricting login to a single database only (no
visible table spaces, groups or roles)
|
Список | pgadmin-support |
Hi, Le 12/05/2010 22:44, Bryce Nesbitt a écrit : > I have a working setup with pgAdmin III, but wish to restrict my user > more. This user currently logs in to a postgres 8.3 cluster that has 5 > databases, but their role only has SELECT on one of the databases. > Yet each time they log in they see all the database names, all the > role names, and all the group names. How can I focus them just a > subset of the tree? > > I am reading from: http://www.pgadmin.org/docs/dev/connect.html > "The maintenance DB field is used to specify the initial database that > pgAdmin connects to, and that will be expected to have the pgAgent > schema andadminpack objects installed (both optional)." > > When I set "Maintenace DB" to the target database, pgAdmin III comes > up fine, but I still see all the role names, group names, and other > database names for the entire cluster. This is despite the fact the > target database has no pgAgent schema. > > If I add a line to "DB restriction" with the word "production" I get: > ERROR: column "production" does not exist > LINE 7: WHERE datname IN (prodiction) > You need to put quotes, as in 'production'. Or if you want more than one restricted db: 'db1','db2' -- Guillaume.http://www.postgresqlfr.orghttp://dalibo.com
В списке pgadmin-support по дате отправления: