Re: Re: Sure enough, the lock file is gone

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
Cc: The Hermit Hacker <scrappy(at)hub(dot)org>, Florent Guillaume <efgeor(at)noos(dot)fr>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: Sure enough, the lock file is gone
Date: 2001-01-27 19:58:59
Message-ID: Pine.LNX.4.30.0101272055020.1492-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Lamar Owen writes:

> I understand why the socket needs to be in /tmp, but why the lockfile?

The lock file protects the Unix domain socket. Consequently, the name of
the lock file needs to be derivable from the name of the socket file, and
vice versa. Also, the name of the socket file must not vary with other
parameters such as installation layout.

> Lock file cleanup should be the responsibility of the script that starts
> postmaster

The postmaster does that itself. That's why the pid is in there.

--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-01-27 20:25:31 Re: Re: Sure enough, the lock file is gone
Previous Message Lamar Owen 2001-01-27 19:56:36 Re: Re: Sure enough, the lock file is gone