Re: We should Axe /contrib/start-scripts - Mailing list pgsql-hackers

From Greg Stark
Subject Re: We should Axe /contrib/start-scripts
Date
Msg-id 407d949e0908261727h14c01ecagfe6fcebce9c650b4@mail.gmail.com
Whole thread Raw
In response to Re: We should Axe /contrib/start-scripts  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: We should Axe /contrib/start-scripts  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Aug 27, 2009 at 1:01 AM, Tom Lane<tgl@sss.pgh.pa.us> wrote:
>> So with this change you would have the startup script not remove the
>> lock file?
>
> Huh?  The startup script shouldn't *ever* remove the lock file.
> That's been true all along, and this doesn't change it.

I thought that was the whole difference between using pg_ctl to start
up and the initscripts. Since the init script knows it's starting
something up at boot time it knows any lock files are left over and
might contain the pid of one of the  other processes the init script
starts.

I did have another thought. It could compare the time from uptime to
the timestamp on the lock file. If the server's been restarted since
the time in the lock file then it must be stale. uhm. unless clock's
been changed...

--
greg
http://mit.edu/~gsstark/resume.pdf


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: MySQL Compatibility WAS: 8.5 release timetable, again
Next
From: Tom Lane
Date:
Subject: Re: We should Axe /contrib/start-scripts