By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
428,759 Members | 1,727 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 428,759 IT Pros & Developers. It's quick & easy.

How to hide database structure

P: n/a
How can I hide all details from users regarding data and structure,
limiting access to data through functions I create?

I don't want a user to be able to see the structure of a table with \d
{tablename} in psql.

TIA
Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
On Mon, Dec 22, 2003 at 09:10:43 -0800,
Michael Gill <my***@usa.com> wrote:
How can I hide all details from users regarding data and structure,
limiting access to data through functions I create?

I don't want a user to be able to see the structure of a table with \d
{tablename} in psql.


Don't give them any direct access to the tables and use a security definer
function to give them indirect access.

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Nov 12 '05 #2

P: n/a
On Tue, Dec 23, 2003 at 22:04:56 -0600,
Bruno Wolff III <br***@wolff.to> wrote:
On Mon, Dec 22, 2003 at 09:10:43 -0800,
Michael Gill <my***@usa.com> wrote:
How can I hide all details from users regarding data and structure,
limiting access to data through functions I create?

I don't want a user to be able to see the structure of a table with \d
{tablename} in psql.


Don't give them any direct access to the tables and use a security definer
function to give them indirect access.


I made a mistake. The above only limits access to the data. You can't
limit access to the structure while allowing direct access to the database.
You will need to create a proxy application/server if you want to do this.

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

Nov 12 '05 #3

P: n/a
If we can limit select privilege, can't we do so on the system tables
that hold metadata? Isn't that what's accessed when a user enters \d
{tablename} ?
br***@wolff.to (Bruno Wolff III) wrote in message news:<20******************@wolff.to>...
On Tue, Dec 23, 2003 at 22:04:56 -0600,
Bruno Wolff III <br***@wolff.to> wrote:
On Mon, Dec 22, 2003 at 09:10:43 -0800,
Michael Gill <my***@usa.com> wrote:
How can I hide all details from users regarding data and structure,
limiting access to data through functions I create?

I don't want a user to be able to see the structure of a table with \d
{tablename} in psql.


Don't give them any direct access to the tables and use a security definer
function to give them indirect access.


I made a mistake. The above only limits access to the data. You can't
limit access to the structure while allowing direct access to the database.
You will need to create a proxy application/server if you want to do this.

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.