pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Heather Johnson <hjohnson@nypost.com>
To: Michael Fuhr <mike@fuhr.org>
Cc: pgsql-admin@postgresql.org
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] How to Prevent Certain Kinds of Joins?
Date: Tue, 22 Feb 2005 15:30:44 -0500
Message-ID: <421B9674.4060807@nypost.com> (raw)
In-Reply-To: <20050222200915.GA71591@winnie.fuhr.org>
References: <421B8D2D.6050800@nypost.com>
	<20050222200915.GA71591@winnie.fuhr.org>

One of the tables contains personally identifiable information (PII) 
(e.g., email, first and last name, etc.). The other contains "click 
stream" data (information about where on our website users have gone). 
In order to be sensitive to users privacy, we don't want to ever (even 
accidentally) run queries that would combine PII and click stream data. 
So we're looking for ways to put "walls" up against combining the data. 
We understand that anyone with ample access to the database can 
deliberately combine the data if they chose to do so in blatent 
violation of our policies. But we want to set something up that would 
put an obstacle or two in the path of anyone who might accidentally run 
such a query.

The ideas about setting up views might work. I guess we'd just have to 
change the permissions of users who have access to the db so that they 
can only use the views and not query the tables directly.

Michael Fuhr wrote:
> On Tue, Feb 22, 2005 at 02:51:09PM -0500, Heather Johnson wrote:
> 
> 
>>Is there a way to revoke permission to join two or more tables, even for 
>>users who have all other permissions (e.g., select, insert, update, 
>>delete) on those tables?
> 
> 
> For what purpose?  If this were possible, then users could still
> do joins on the client side if they had access to all the data.
> Are you just trying to prevent potentially large queries?  What
> problem are you trying to solve?
> 



view thread (7+ messages)  latest in thread

Message-ID: <421B9674.4060807@nypost.com>
Permalink:  ../421B9674.4060807@nypost.com/
Also on:    postgresql.org/message-id/421B9674.4060807@nypost.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: hjohnson@nypost.com, mike@fuhr.org, pgsql-general@postgresql.org
  Subject: Re: [GENERAL] How to Prevent Certain Kinds of Joins?
  In-Reply-To: <421B9674.4060807@nypost.com>
  References: <421B8D2D.6050800@nypost.com> <20050222200915.GA71591@winnie.fuhr.org> <421B9674.4060807@nypost.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox