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

From Brook Milligan
Subject Re: [HACKERS] postmaster crash and .s.pgsql file
Date
Msg-id 199801291506.IAA24989@trillium.nmsu.edu
Whole thread Raw
In response to Re: [HACKERS] postmaster crash and .s.pgsql file  (The Hermit Hacker <scrappy@hub.org>)
Responses Re: [HACKERS] postmaster crash and .s.pgsql file  (Bruce Momjian <maillist@candle.pha.pa.us>)
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.

Cheers,
Brook

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Profiling the backend (gprof output) [current devel]
Next
From: darrenk@insightdist.com (Darren King)
Date:
Subject: Error in nodes/parse_node.h