pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Jeff - <threshar@torgo.978.org>
Cc: pgsql-docs@postgresql.org
Subject: Re: SELinux & Redhat
Date: Fri, 06 May 2005 11:28:42 -0400
Message-ID: <14759.1115393322@sss.pgh.pa.us> (raw)
In-Reply-To: <200505061713.40511.peter_e@gmx.net>
References: <200505061455.j46Etej28299@candle.pha.pa.us>
	<200505061713.40511.peter_e@gmx.net>

Peter Eisentraut <peter_e@gmx.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



view thread (11+ messages)  latest in thread

Message-ID: <14759.1115393322@sss.pgh.pa.us>
Permalink:  ../14759.1115393322@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/14759.1115393322@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, peter_e@gmx.net, pgman@candle.pha.pa.us, threshar@torgo.978.org, pgsql-docs@postgresql.org
  Subject: Re: SELinux & Redhat
  In-Reply-To: <14759.1115393322@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox