Re: Restricting login to a single database only (no visible table spaces, groups or roles)

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Bryce Nesbitt <bnesbitt(at)bepress(dot)com>
Cc: pgadmin-support(at)postgresql(dot)org
Subject: Re: Restricting login to a single database only (no visible table spaces, groups or roles)
Date: 2010-05-13 17:40:24
Message-ID: 4BEC3988.4070703@lelarge.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Le 13/05/2010 06:20, Bryce Nesbitt a écrit :
> On Wed, May 12, 2010 at 4:00 PM, Guillaume Lelarge
> <guillaume(at)lelarge(dot)info> wrote:
>> If you use the "DB restriction" field, you should see only the
>> restricted databases. Users and groups will still be available.
>
> That's what I see. As a feature request then: have a way to suppress
> all but the active database.
> No Tablespaces, Groups Roles, No Login Roles.
>

I don't think pgAdmin can do something about it. The first user that
will execute a "SELECT * FROM pg_database" will see all the existing
databases. Needless to say that he can do that for the other global
objects (roles, tablespaces).

--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com

In response to

Browse pgadmin-support by date

  From Date Subject
Next Message Richard Broersma 2010-05-14 17:19:42 reporting feature request
Previous Message Bryce Nesbitt 2010-05-13 04:20:52 Re: Restricting login to a single database only (no visible table spaces, groups or roles)