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 14:44:17
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> > 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.
> The OS-specific areas would be a nice feature, but not for this release
> of course. We could either put in the hooks to specify the area now, and
> default to /tmp, or we could put that off until December.
> Perhaps Billy and I can work it through then...

Yes, let's wait.  I don't want another round of 'My OS has ...' at this
point in the release cycle.  I think Marc would have a heart attack.

  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: Thomas G. LockhartDate: 1998-10-12 14:58:28
Subject: Re: [HACKERS] dynamic libraries
Previous:From: Thomas G. LockhartDate: 1998-10-12 14:38:44
Subject: Re: [HACKERS] postmaster locking issues.

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