Message-ID: <4D790C0F.3080100@iii.com>
Date: Thu, 10 Mar 2011 09:36:15 -0800
From: Dinesh Bhandary <dbhandary@iii.com>
Reply-To: dbhandary@iii.com
Organization: Innovative Interfaces
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: pgsql-admin@postgresql.org
Subject: Re: hiding metadata information from a user
References: <4D781A21.8030109@iii.com>
In-Reply-To: <4D781A21.8030109@iii.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

It is a follow up to my first question. I am still interested in knowing 
if we can create a pure read only user in postgres, which has no access 
to system catalogs.

The alternative I am thinking is using a separate instance and use 
dblink or replication tool to refresh data. Do you know if we can hide 
connection details from a user if we use dblink? I just want to make 
sure this read only
user does not go and query our system catalogs in production server. 
Dblink should be easier to implement than using replication tool.

Thanks.
Dinesh

On 3/9/2011 4:24 PM, Dinesh Bhandary wrote:
> Hi All -
>
> Please let me know if this is possible to do in postgres.
>
> I am creating a read only user, which has limited access to db 
> objects, primarily views. Even though this user can't query data from 
> other db objects it can view the system catalog using pg* views and 
> tables, thereby exposing our logical schema.
> Is there a way in postgres to limit access to system catalogs. I just 
> want a pure read only user, which can do nothing but query specific 
> views we outlined.
>
> Thanks!
> Dinesh
>