| From: | "Robert Haas" <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "KaiGai Kohei" <kaigai(at)ak(dot)jp(dot)nec(dot)com> |
| Cc: | "Bruce Momjian" <bruce(at)momjian(dot)us>, "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 12:05:07 |
| Message-ID: | 603c8f070809250505k6622e90fo899e8959a22e1081@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Are you saying the performance penalty when full functionalities are
> enabled?
> (The meaning of "bells and whistles" is unclear for me.)
Yes, that's what I meant. (Sorry.)
> We can show it on the page.22 of my presentation in PGcon2008.
> http://www.pgcon.org/2008/schedule/attachments/38_pgcon2008-sepostgresql.pdf
>
> It shows about 10% of penalty in maximum in pgbench, and larger database
> tend to have relatively less performance penalty.
That doesn't really sound too bad if you are operating in an
environment where security is paramount. Of course, if your vendor
enables SELinux and SEPostgresql by default (even though you don't
really care) then it might not be so good.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-09-25 12:14:46 | Re: PostgreSQL future ideas |
| Previous Message | Zeugswetter Andreas OSB sIT | 2008-09-25 10:34:25 | Re: Transaction Snapshots and Hot Standby |