From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Jeff - <threshar(at)torgo(dot)978(dot)org>, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: SELinux & Redhat |
Date: | 2005-05-06 15:28:42 |
Message-ID: | 14759.1115393322@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-performance |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Am Freitag, 6. Mai 2005 16:55 schrieb Bruce Momjian:
>> A blurb about what? No one else has reported such a problem so we have
>> no reason to assume it isn't a misconfiguration on your end.
> *Countless* people are constantly reporting problems that can be
> attributed to selinux.
That's mostly because selinux outright broke postgres in the initial
FC3 releases :-(. I have to take most of the blame for this myself;
I didn't realize there might be problems, and didn't test adequately.
I believe the problems are all resolved in the latest Fedora RPMs,
though this pg_dump report may be something new.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Devrim GUNDUZ | 2005-05-06 15:33:20 | Re: SELinux & Redhat |
Previous Message | Tom Lane | 2005-05-06 15:23:54 | Re: SELinux & Redhat |
From | Date | Subject | |
---|---|---|---|
Next Message | Devrim GUNDUZ | 2005-05-06 15:33:20 | Re: SELinux & Redhat |
Previous Message | Tom Lane | 2005-05-06 15:23:54 | Re: SELinux & Redhat |