Received: from maia.hub.org (maia-5.hub.org [200.46.204.29])
	by mail.postgresql.org (Postfix) with ESMTP id 59A346329B6
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Thu, 26 Aug 2010 19:01:34 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024)
	with ESMTP id 05280-01 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Thu, 26 Aug 2010 22:01:26 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by mail.postgresql.org (Postfix) with ESMTP id 4CDD6632BC9
	for <pgsql-admin@postgresql.org>; Thu, 26 Aug 2010 19:01:26 -0300 (ADT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o7QM1FJZ000610;
	Thu, 26 Aug 2010 18:01:15 -0400 (EDT)
To: Greg Smith <greg@2ndquadrant.com>, xsun <xu2002261@163.com>,
	pgsql-admin@postgresql.org
Subject: Re: The function of lock file named ".s.PGSQL.<port>.lock" on Linux? 
In-reply-to: <23168.1281488995@sss.pgh.pa.us> 
References: <i399mq$28vn$1@news.hub.org> <16464.1281026474@sss.pgh.pa.us>
	<4C61F3FF.1080303@2ndquadrant.com> <23168.1281488995@sss.pgh.pa.us>
Comments: In-reply-to Tom Lane <tgl@sss.pgh.pa.us>
	message dated "Tue, 10 Aug 2010 21:09:55 -0400"
Date: Thu, 26 Aug 2010 18:01:15 -0400
Message-ID: <609.1282860075@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201008/238
X-Sequence-Number: 35487

Greg Smith <greg@2ndquadrant.com> writes:
>> 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?

Done.

			regards, tom lane