Skip site navigation (1) Skip section navigation (2)

Re: question/problem concerning GRANT/REVOKE

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: "Gerhard Wohlgenannt" <wohlg(at)ai(dot)wu-wien(dot)ac(dot)at>
Cc: pgsql-general(at)postgresql(dot)org, "albert weichselbraun" <albert(dot)weichselbraun(at)wu-wien(dot)ac(dot)at>
Subject: Re: question/problem concerning GRANT/REVOKE
Date: 2008-04-30 19:28:36
Message-ID: dcc563d10804301228w24ef2ee3u3af4c18a47d077a7@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-general
On Tue, Apr 29, 2008 at 2:46 AM, Gerhard Wohlgenannt
<wohlg(at)ai(dot)wu-wien(dot)ac(dot)at> wrote:
> hi!
>
>  I have a pretty basic problem: We have several schemas in one of our
> databases, and we need the users to see only the tables (and table
> structure) of tables inside their own schema.  So I created schemas for
> those users, and set their "search_path".
>
>  But with \d public.<tab key> users can see all tables (and their structure)
> in the public (and other) schemas -- and I found no way yet to prevent
> this??
>  I have tried "REVOKE ALL" from the database itself, and the other schemas,
> and single tables -- for the specific user, and also for the user "PUBLIC"
> -- but it had no effect!
>  How can I prevent exposing the structure of all tables in the database to
> user that should work in their SCHEMA?
>
>  Help would be appreciated very much!! :-)

This is a semi frequently asked question.  There's no mechanism built
into pgsql that allows you to hide other schemas and objects this way.

Note that if you have the proper security setup, all they can do is
see that the other tables are there.

In response to

pgsql-general by date

Next:From: Bayless KirtleyDate: 2008-04-30 19:56:49
Subject: Closed ResultSet error
Previous:From: BenoƮt CarpentierDate: 2008-04-30 18:59:12
Subject: Benetl 1.8, free ETL tool using postgreSQL is out !!!

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group