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

Re: [HACKERS] postmaster locking issues.

From: "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
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:38:44
Message-ID: 36221474.45CF1969@alumni.caltech.edu (view raw or flat)
Thread:
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...

                       - Tom

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 1998-10-12 14:44:17
Subject: Re: [HACKERS] postmaster locking issues.
Previous:From: Bruce MomjianDate: 1998-10-12 14:06:57
Subject: Re: [HACKERS] Minor problem with Solaris 2.7beta

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