Re: 8.4 release planning - Mailing list pgsql-hackers

From Tom Lane
Subject Re: 8.4 release planning
Date
Msg-id 22203.1233086866@sss.pgh.pa.us
Whole thread Raw
In response to Re: 8.4 release planning  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: 8.4 release planning  (Joshua Brindle <method@manicmethod.com>)
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:
> On Tue, 2009-01-27 at 13:57 -0500, Joshua Brindle wrote:
>> Josh Berkus wrote:
>>> Hmmm.  Why try to hide individual rows in tables then?  That would seem 
>>> not in keeping with the filesystem policies.
>> 
>> Because rows have data in them. It is analogous to not allowing the contents of 
>> the file to be visible. However, the primary key is still known to exist through 
>> various means, which is more analogous to the filename.

> Since most keys are likely to be non-meaningful IDs, its not going to
> help you much.

Even more to the point: if the expectation is that you can hide a row's
data payload but not its primary key, you can accomplish that with
column-level permissions, without having to get into any non-standard
or even faintly surprising SQL behavior,
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: 8.4 release planning
Next
From: Tom Lane
Date:
Subject: Re: 8.4 release planning (was Re: [COMMITTERS] pgsql: Automatic view update rules)