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

Re: [HACKERS] postmaster locking issues.

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: lockhart(at)alumni(dot)caltech(dot)edu (Thomas G(dot) Lockhart)
Cc: Bill(dot)Allie(at)mug(dot)org, tgl(at)sss(dot)pgh(dot)pa(dot)us, taral(at)mail(dot)utexas(dot)edu, hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] postmaster locking issues.
Date: 1998-10-12 13:48:50
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> > >> 5.  The port lock will be kept in '/var/opt/pgsql/lock/'.
> As everyone has pointed out, we can't count on a specific convention for
> where the lock file should go. However, we can probably count on a
> convention to be followed on a particular OS. That would seem to be
> something to define in Makefile.port, which could then be overridden by
> a configure option or Makefile.custom entry.
> On my RedHat Linux systems, the appropriate place seems to be /var/lock
> or /var/lock/pgsql.

I have talked to Billy.  I see no real value to try chasing around
OS-specific lock file locations.  /tmp is fine, and if they don't have
sticky bits in /tmp, they have much larger problems than the location of
the lock file.

  Bruce Momjian                        |
  maillist(at)candle(dot)pha(dot)pa(dot)us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 1998-10-12 14:06:57
Subject: Re: [HACKERS] Minor problem with Solaris 2.7beta
Previous:From: Bruce MomjianDate: 1998-10-12 13:47:39
Subject: Re: [HACKERS] Open 6.4 items

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