| From: | tgl(at)svr1(dot)postgresql(dot)org (Tom Lane) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql-server: Adjust postmaster to recognize that a lockfile containing |
| Date: | 2004-10-01 18:30:27 |
| Message-ID: | 20041001183027.4E76332A22A@svr1.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-10-01 20:39:55 | pgsql-server: fmgr_security_definer had better do a PG_TRY to ensure the |
| Previous Message | User Mha | 2004-10-01 18:21:06 | pginstaller - pginst: Don't crash when installing as a service but not |