From: | Oliver Elphick <olly(at)lfix(dot)co(dot)uk> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Vince Vielhaber <vev(at)michvhf(dot)com>, "J(dot) M(dot) Brenner" <doom(at)kzsu(dot)stanford(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: location of the configuration files |
Date: | 2003-02-14 06:26:12 |
Message-ID: | 1045203972.10910.107.camel@linda.lfix.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 2003-02-14 at 02:49, Tom Lane wrote:
> Oliver Elphick <olly(at)lfix(dot)co(dot)uk> writes:
> > I'm not entirely sure why SE Linux has a problem, seeing that postgres
> > needs read-write access to all the files in $PGDATA, but assuming the
> > need is verified, I could do this by moving the pid file from
> > $PGDATA/postmaster.pid to /var/run/postgresql/5432.pid and similarly for
> > other ports. This would also have the benefit of being more FHS
> > compliant What do people think about that?
>
> No chance at all. Breaking the connection between the data directory
> and the postmaster.pid file means we don't have an interlock against
> starting two postmasters in the same data directory.
Yes; that would take a lot of effort to get round. Not worth it, I
think.
> I do not see the argument for moving the pid file anyway. Surely no
> one's going to tell us that the postmaster shouldn't have write access
> to the data directory?
I'm waiting for a response on that one; I don't understand it either.
--
Oliver Elphick Oliver(dot)Elphick(at)lfix(dot)co(dot)uk
Isle of Wight, UK http://www.lfix.co.uk/oliver
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C
========================================
"God be merciful unto us, and bless us; and cause his
face to shine upon us." Psalms 67:1
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-02-14 06:30:21 | Re: location of the configuration files |
Previous Message | Oliver Elphick | 2003-02-14 06:18:22 | Re: location of the configuration files |