| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Joshua Brindle <method(at)manicmethod(dot)com>, Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>, Josh Berkus <josh(at)agliodbs(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>, Gregory Stark <stark(at)enterprisedb(dot)com>, 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-28 22:45:31 |
| Message-ID: | 4640.1233182731@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Tom Lane wrote:
>> As the SEPostgres patch is constructed, the planner could *never* trust
>> an FK for optimization since it would have no way to know whether row
>> level permissions might be present (perhaps only for some rows) at
>> execution time. You could only get back the optimization in builds with
>> SEPostgres compiled out. That's pretty nasty, especially for packagers
>> who have to decide which build setting will displease fewer users.
> I am afraid that SQL-level row permissions would also cause that
> problem, and I thought they were enabled by default. (The configure
> flag --enable-selinux only controls SE-Linux support.)
So they would. However, I've already determined that I'm against
row-level permissions of either flavor ;-)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua Brindle | 2009-01-28 22:47:00 | Re: How to get SE-PostgreSQL acceptable |
| Previous Message | Bruce Momjian | 2009-01-28 22:44:06 | Re: 8.4 release planning |