| From: | KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Proposal of SE-PostgreSQL patches (for CommitFest:Sep) |
| Date: | 2008-09-25 00:26:06 |
| Message-ID: | 48DADA9E.3050403@ak.jp.nec.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian wrote:
> Robert Haas wrote:
>>> The objection comes down to this: it's an extremely large, invasive,
>>> and probably performance-losing patch, which apparently will be of use
>>> to only a rather small set of people. It's not unreasonable to discuss
>>> just how large that set might be while we debate whether to accept the
>>> patch.
>> Significant loss of performance for people who are not using the
>> feature seems like it ought to be considered a non-starter. "Not
>> using MAC" needs to be a fast-path.
>
> Right now all of SE-PostgreSQL is a compile-time option so I assume the
> slowdown is only for compile-enabled builds.
Yes, we need '--enable-selinux' to activate all of SE-PostgreSQL features.
In addition, these are invoked via security hooks which are declared
as inline functions. So, I think it does not give us additional loss of
performances when you don't add the compile time option explicitly.
Thanks,
--
OSS Platform Development Division, NEC
KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2008-09-25 00:46:31 | Re: Proposal of SE-PostgreSQL patches (for CommitFest:Sep) |
| Previous Message | KaiGai Kohei | 2008-09-25 00:19:54 | Re: Proposal of SE-PostgreSQL patches (for CommitFest:Sep) |