From: | Joshua Brindle <method(at)manicmethod(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Gregory Stark <stark(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Simon Riggs <simon(at)2ndQuadrant(dot)com>, Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Bernd Helmle <mailings(at)oopsware(dot)de>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: 8.4 release planning |
Date: | 2009-01-27 18:57:26 |
Message-ID: | 497F5916.1060803@manicmethod.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-01-27 18:58:33 | Re: Commitfest infrastructure (was Re: 8.4 release planning) |
Previous Message | Zdenek Kotala | 2009-01-27 18:57:05 | Re: pg_upgrade project status |