Skip site navigation (1) Skip section navigation (2)

postmaster locking issues.

From: "Billy G(dot) Allie" <Bill(dot)Allie(at)mug(dot)org>
To: hackers(at)postgreSQL(dot)org
Subject: postmaster locking issues.
Date: 1998-10-11 00:47:35
Message-ID: 199810110047.UAA27416@bgalli.mug.org (view raw or flat)
Thread:
Lists: pgsql-hackers
After looking into the issue of using PID file locks vs. flock/unlock, I have 
come to the following conclusions:

1.  It is generally agreed that a PID lock file should replace the current me-
    thod of locking (fcntl based locking). (See the message thread with
    '[HACKERS] flock patch breaks things here' in the subject).

2.  The purpose of the lock file is to prevent multiple postmasters from run-
    ning on the same port and database.

3.  Two PID files will be necessary, one to prevent mulitple instances of post-
    masters from running against the same data base, and one to prevent 
multiple
    instances from using the same port.

4.  The database lock will be located in the DATA directory being locked.

5.  The port lock will be kept in '/var/opt/pgsql/lock/'.

Comments, questions, concerns?

-- 
____       | Billy G. Allie    | Domain....: Bill(dot)Allie(at)mug(dot)org
|  /|      | 7436 Hartwell     | Compuserve: 76337,2061
|-/-|----- | Dearborn, MI 48126| MSN.......: B_G_Allie(at)email(dot)msn(dot)com
|/  |LLIE  | (313) 582-1540    | 



Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 1998-10-11 01:35:47
Subject: Re: [HACKERS] postmaster locking issues.
Previous:From: Billy G. AllieDate: 1998-10-11 00:27:06
Subject: PostgreSQL 6.4 patches - portability related.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group