5 Commits (02490d4692c46bee3e9279e79c5d07c576d2a32c)

Author	SHA1	Message	Date
Tom Lane	8f5500e6bd	Make it reasonably safe to use pg_ctl to start the postmaster from a boot-time ... script. To do this, have pg_ctl pass down its parent shell's PID in an environment variable PG_GRANDPARENT_PID, and teach CreateLockFile() to disregard that PID as a false match if it finds it in postmaster.pid. This allows us to cope with one level of postgres-owned shell process even with pg_ctl in the way, so it's just as safe as starting the postmaster directly. You still have to be careful about how you write the initscript though. Adjust the comments in contrib/start-scripts/ to not deprecate use of pg_ctl. Also, fix the ROTATELOGS option in the OSX script, which was indulging in exactly the sort of unsafe coding that renders this fix pointless :-(. A pipe inside the "sudo" will probably result in more than one postgres-owned process hanging around.	17 years ago
Tom Lane	c8196c87a7	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.	22 years ago
PostgreSQL Daemon	969685ad44	$Header: -> $PostgreSQL Changes ...	22 years ago
Peter Eisentraut	031e1afa23	Pass -D option to pg_ctl because export PGDATA won't be preserved across ... 'su -l'. Reported by <VASQUEZ_JASON@LILLY.COM>.	25 years ago
Peter Eisentraut	fdf87fdf7b	Add new FreeBSD start script that makes use of new pg_ctl functionality.	25 years ago