pgsql: Treat EPERM as a non-error case when checking to see if old

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Treat EPERM as a non-error case when checking to see if old
Date: 2005-03-18 03:49:22
Message-ID: 20050318034922.5154A5655C@svr1.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Treat EPERM as a non-error case when checking to see if old postmaster
is still alive. This improves our odds of not getting fooled by an
unrelated process when checking a stale lock file. Other checks already
in place, plus one newly added in checkDataDir(), ensure that we cannot
attempt to usurp the place of a postmaster belonging to a different userid,
so there is no need to error out. Add comments indicating the importance
of these other checks.

Tags:
----
REL8_0_STABLE

Modified Files:
--------------
pgsql/src/backend/postmaster:
postmaster.c (r1.443 -> r1.443.4.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/postmaster.c.diff?r1=1.443&r2=1.443.4.1)
pgsql/src/backend/utils/init:
miscinit.c (r1.137 -> r1.137.4.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/init/miscinit.c.diff?r1=1.137&r2=1.137.4.1)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2005-03-18 05:24:14 pgsql: Need to release buffer pins before attempting to drop files
Previous Message Tom Lane 2005-03-18 03:48:51 pgsql: Treat EPERM as a non-error case when checking to see if old