Re: Re: Sure enough, the lock file is gone - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Re: Sure enough, the lock file is gone
Date
Msg-id Pine.LNX.4.30.0101272055020.1492-100000@peter.localdomain
Whole thread Raw
In response to Re: Re: Sure enough, the lock file is gone  (Lamar Owen <lamar.owen@wgcr.org>)
List 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@gmx.net       http://yi.org/peter-e/



pgsql-hackers by date:

Previous
From: Lamar Owen
Date:
Subject: Re: Re: Sure enough, the lock file is gone
Next
From: Lamar Owen
Date:
Subject: Re: Re: Sure enough, the lock file is gone