Log Message:
-----------
Adjust postmaster to recognize that a lockfile containing its parent's PID
must be stale. Tweak example startup scripts to not use pg_ctl but launch
the postmaster directly, thereby ensuring that only the postmaster's direct
parent shell will be a postgres-owned process. In combination these should
fix the longstanding problem of the postmaster sometimes refusing to start
during reboot because it thinks the old lockfile is not stale.
Modified Files:
--------------
pgsql-server/contrib/start-scripts:
PostgreSQL.darwin (r1.3 -> r1.4)
(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/contrib/start-scripts/PostgreSQL.darwin.diff?r1=1.3&r2=1.4)
freebsd (r1.3 -> r1.4)
(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/contrib/start-scripts/freebsd.diff?r1=1.3&r2=1.4)
linux (r1.6 -> r1.7)
(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/contrib/start-scripts/linux.diff?r1=1.6&r2=1.7)
pgsql-server/src/backend/utils/init:
miscinit.c (r1.132 -> r1.133)
(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/backend/utils/init/miscinit.c.diff?r1=1.132&r2=1.133)
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
