Re: The function of lock file named ".s.PGSQL..lock" on Linux? - Mailing list pgsql-admin

From Greg Smith
Subject Re: The function of lock file named ".s.PGSQL..lock" on Linux?
Date
Msg-id 4C61F3FF.1080303@2ndquadrant.com
Whole thread Raw
In response to Re: The function of lock file named ".s.PGSQL..lock" on Linux?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: The function of lock file named ".s.PGSQL..lock" on Linux?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
Tom Lane wrote:
> We can't portably lock the socket file itself, so we make a separate
> ordinary file for locking purposes.
>

It looks to me like the fact that the .lock file is created is only
documented in src/backend/utils/init/miscinit.c , and even there the
reason why (what you wrote above) isn't mentioned.  Seems like noting
this file is created in the unix_socket_directory entry of the docs, and
the rationale for why in the source code, would make a useful
improvement.  Anybody want to write a little documentation patch?

--
Greg Smith  2ndQuadrant US  Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com   www.2ndQuadrant.us


pgsql-admin by date:

Previous
From: Kasia Tuszynska
Date:
Subject: Re: postgres function does not handle PUBLIC - expected?
Next
From: Tom Lane
Date:
Subject: Re: The function of lock file named ".s.PGSQL..lock" on Linux?