Re: Using an alternate PGDATA on RHEL4 with SELinux enabled - Mailing list pgsql-general

From Tom Lane
Subject Re: Using an alternate PGDATA on RHEL4 with SELinux enabled
Date
Msg-id 21422.1154097323@sss.pgh.pa.us
Whole thread Raw
In response to Re: Using an alternate PGDATA on RHEL4 with SELinux enabled  ("David Esposito" <pgsql-general@esposito.newnetco.com>)
List pgsql-general
"David Esposito" <pgsql-general@esposito.newnetco.com> writes:
>> -----Original Message-----
>> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
>> The default selinux policy prevents postgres from writing anywhere
>> except under /var/lib/pgsql.  If you want a nondefault PGDATA location
>> then you have to tweak the policy.

> It's not that simple ... if I su to postgres, I can initdb and launch
> postmaster in any directory I wish (as long as it has rwx for the postgres
> user) ... it's only if I try to do this from the init.d start script that
> the problem occurs ...

Yes, it is that simple.  Processes launched from start scripts inherit
a different (much more restrictive) selinux context than ones launched
from interactive shells.

            regards, tom lane

pgsql-general by date:

Previous
From: Jessica M Salmon
Date:
Subject: Re: loop with circular updates
Next
From: Michael Fuhr
Date:
Subject: Re: Create spatial_ref_sys entry from srtext ?