Re: file-locking and postmaster.pid - Mailing list pgsql-hackers

From korry
Subject Re: file-locking and postmaster.pid
Date
Msg-id 1148497426.21335.46.camel@sakai.localdomain
Whole thread Raw
In response to file-locking and postmaster.pid  (Andreas Joseph Krogh <andreak@officenet.no>)
List pgsql-hackers
<blockquote type="CITE"><pre>
<font color="#000000">I'm sure there's a good reason for having it the way it is, having so many </font>
<font color="#000000">smart knowledgeable people working on this project. Could someone please </font>
<font color="#000000">explain the rationale of the current solution to me?</font>
</pre></blockquote><pre>

</pre> We've ignored Andreas' original question.  Why not use a lock to indicate that the postmaster is still running? 
Atfirst blush, that seems more reliable than checking for a (possibly recycled) process ID.<br /><br /><br />
           -- Korry<br /><br /> 

pgsql-hackers by date:

Previous
From: Andreas Joseph Krogh
Date:
Subject: Re: file-locking and postmaster.pid
Next
From: korry
Date:
Subject: Re: file-locking and postmaster.pid