Skip site navigation (1) Skip section navigation (2)

Re: possible bug...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Prasad Duggineni" <pduggineni(at)prominencenet(dot)com>
Cc: srikumar(dot)kareti(at)spanlink(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: possible bug...
Date: 2005-09-22 15:23:04
Message-ID: 29140.1127402584@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"Prasad Duggineni" <pduggineni(at)prominencenet(dot)com> writes:
> Try turning the enforcement mode off. 

Or put the data directory where the standard selinux policy expects it
to be, namely /var/lib/pgsql/data.

The lack of any useful error message is a selinux policy bug, which
appears to be fixed in reasonably-current FC4 (I've got
selinux-policy-targeted-1.25.4-10, and I don't see it).

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2005-09-22 15:35:17
Subject: Re: BUG #1904: using distinct with null col causes error
Previous:From: Prasad DuggineniDate: 2005-09-22 14:41:01
Subject: Re: possible bug...

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group