Horton

Re: 8.4 release planning

Joshua Brindle <method@manicmethod.com>

View thread View on postgr.es
From: Joshua Brindle <method@manicmethod.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: Stephen Frost <sfrost@snowman.net>, Gregory Stark <stark@enterprisedb.com>, Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>, Simon Riggs <simon@2ndQuadrant.com>, Ron Mayer <rm_pg@cheapcomplexdevices.com>, "Joshua D. Drake" <jd@commandprompt.com>, Merlin Moncure <mmoncure@gmail.com>, "Jonah H. Harris" <jonah.harris@gmail.com>, Bruce Momjian <bruce@momjian.us>, Bernd Helmle <mailings@oopsware.de>, Peter Eisentraut <peter_e@gmx.net>, pgsql-hackers@postgresql.org
Date: 2009-01-27T18:57:26Z
Lists: pgsql-hackers 
Josh Berkus wrote:
> Josh,
> 
>> We do not consider that a short coming, anyone who needs to hide 
>> existence of files needs to set up their directory structure to 
>> disallow read/search/create on the directories they aren't allowed to 
>> discover filenames in. Polyinstanciation can also address this issue.
> 
> 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.