Re: [HACKERS] postmaster crash and .s.pgsql file - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] postmaster crash and .s.pgsql file
Date
Msg-id 199801291650.LAA12187@candle.pha.pa.us
Whole thread Raw
In response to Re: [HACKERS] postmaster crash and .s.pgsql file  (Brook Milligan <brook@trillium.NMSU.Edu>)
Responses Re: [HACKERS] postmaster crash and .s.pgsql file  (Brook Milligan <brook@trillium.NMSU.Edu>)
List pgsql-hackers
>
>    > I would opt for /var/run to store the pid files and have the name set to
>
>        That would assume that postmaster runs as root, which is not
>    allowed...has to be in /tmp somewhere
>
> No.  Make /var/run writable by some group (e.g., group pidlog) and put
> postgres (and other things like root or daemon or ..., whatever needs
> to log pid files) in that group.
>
> /var/run really is where a pid file should be.  I submitted a patch
> that would do this some time ago.  I'll resend it if there is
> interest.

We can't expect the user to be able to change /var/run permissions.
Must be in pgsql/ or /tmp.

--
Bruce Momjian
maillist@candle.pha.pa.us

pgsql-hackers by date:

Previous
From: Goran Thyni
Date:
Subject: Re: [HACKERS] postmaster crash and .s.pgsql file
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Error in nodes/parse_node.h