X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id CCE0E8B9CA2; Tue, 22 Feb 2005 20:31:23 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 00988-02; Tue, 22 Feb 2005 20:31:17 +0000 (GMT) Received: from nypost.com (ms1.nypost.com [206.15.109.53]) by svr1.postgresql.org (Postfix) with ESMTP id E47378B9B44; Tue, 22 Feb 2005 20:31:17 +0000 (GMT) Received: from ([10.238.16.157]) by ms1.nypost.com with ESMTP id 4220067.3562077; Tue, 22 Feb 2005 15:30:51 -0500 Message-ID: <421B9674.4060807@nypost.com> Date: Tue, 22 Feb 2005 15:30:44 -0500 From: Heather Johnson User-Agent: Mozilla Thunderbird 0.8 (X11/20041018) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Fuhr Cc: pgsql-admin@postgresql.org, pgsql-general@postgresql.org Subject: Re: [GENERAL] How to Prevent Certain Kinds of Joins? References: <421B8D2D.6050800@nypost.com> <20050222200915.GA71591@winnie.fuhr.org> In-Reply-To: <20050222200915.GA71591@winnie.fuhr.org> X-Enigmail-Version: 0.86.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.234 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE X-Spam-Level: X-Archive-Number: 200502/234 X-Sequence-Number: 16402 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? >