From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
To: | Chris <pglist(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Limiting USAGE to only certain objects within a schema |
Date: | 2005-01-11 16:29:59 |
Message-ID: | 20050111162959.GB4797@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Jan 10, 2005 at 14:40:46 -0800,
Chris <pglist(at)gmail(dot)com> wrote:
> Basically what I want is to limit a user to not being able to view
> certain tables within a schema, in this case the public schema. Say
> we have 300 tables in a database but a particular user only needs
> access to 3 of them. I don't really want them to even be able to view
> all the other tables. Using separate databases isn't possible because
> a web application running under mod perl needs access to all the
> tables, and I don't want to keep a pool of persistant connections open
> for 300+ databases.
>
> I would rather avoid using schema's to do this if I can, but I think
> that's the only way to get what I want.
What do you mean by view other tables? You can see metadata for tables
in the catalog tables and you can't block access to those without causing
problems.
From | Date | Subject | |
---|---|---|---|
Next Message | Nirmalya Lahiri | 2005-01-11 18:16:16 | Re: Private or publice function |
Previous Message | lol | 2005-01-11 16:16:27 | Re: PostgreSQL 8 on windows very slow |