postgres.git / summary / log / commit / refs

commit    efae4653c98fd201a8a723bceabf182a1005ac0f
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Tue May 22 02:10:40 2012 +0000
First released in: 9.2.0

    Update woefully-obsolete comment.
    
    The accurate info about what's in a lock file has been in miscadmin.h
    for some time, so let's just make this comment point there instead of
    maintaining a duplicative copy.


 src/backend/utils/init/miscinit.c | 16 ++++------------
 1 file changed, 4 insertions(+), 12 deletions(-)

diff --git a/src/backend/utils/init/miscinit.c b/src/backend/utils/init/miscinit.c
index 51809b7a88a..0f734260c16 100644
--- a/src/backend/utils/init/miscinit.c
+++ b/src/backend/utils/init/miscinit.c
@@ -629,18 +629,10 @@ GetUserNameFromId(Oid roleid)
  *
  * These routines are used to create both a data-directory lockfile
  * ($DATADIR/postmaster.pid) and a Unix-socket-file lockfile ($SOCKFILE.lock).
- * Both kinds of files contain the same info:
- *
- *		Owning process' PID
- *		Data directory path
- *
- * By convention, the owning process' PID is negated if it is a standalone
- * backend rather than a postmaster.  This is just for informational purposes.
- * The path is also just for informational purposes (so that a socket lockfile
- * can be more easily traced to the associated postmaster).
- *
- * A data-directory lockfile can optionally contain a third line, containing
- * the key and ID for the shared memory block used by this postmaster.
+ * Both kinds of files contain the same info initially, although we can add
+ * more information to a data-directory lockfile after it's created, using
+ * AddToDataDirLockFile().  See miscadmin.h for documentation of the contents
+ * of these lockfiles.
  *
  * On successful lockfile creation, a proc_exit callback to remove the
  * lockfile is automatically created.


[parent: cdf8bcb8d93b]