Re: Permissions to schema

From: TiTo® <tito(at)uel(dot)br>
To: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Permissions to schema
Date: 2009-10-27 10:50:54
Message-ID: 7224758535E74A869B2F335841DFBC06@u176013
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

I thing he is writing about the database objects estructure too. You can avoid users to access data from a schema, but you cant avoid they to access objects structure. As example you will see, on a table, its columns but not its data.

Sergio Tito
----- Original Message -----
From: Scott Mead
To: Eduardo Sá dos Reis
Cc: pgsql-admin(at)postgresql(dot)org
Sent: Monday, October 26, 2009 10:04 AM
Subject: Re: [ADMIN] Permissions to schema

2009/10/26 Eduardo Sá dos Reis <eduardoreis(at)pjf(dot)mg(dot)gov(dot)br>

Hi,

I have the structure on Postgre:

database: dbGlobal

schema1: sch_sist1 owner sch_sist1: john

schema2 sch_sist2 owner sch_sist2: mary

I' m using pgAdmin III.

Is there a way to avoid the mary to access the schema sch_sist1 ?

I don't want that mary see/access the schema of john and I don't want that john see/access the schema of mary.

Anybody has a solution.

http://www.postgresql.org/docs/current/static/sql-revoke.html

kgb=# create schema s1;
CREATE SCHEMA
kgb=# create user mary;
CREATE ROLE
kgb=# revoke all on schema s1 from mary;
REVOKE
kgb=# create table s1.testing (id int);
CREATE TABLE
kgb=# \c kgb mary
kgb=> set search_path=s1;
SET
kgb=> \dt
No relations found.
kgb=> select * from s1.testing;
ERROR: permission denied for schema s1
kgb=>

--Scott

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message David F. Skoll 2009-10-27 11:32:29 Re: Warm standby problems
Previous Message Andreas Schmidt 2009-10-27 07:53:00 Re: pg_standby doesnt't work