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

Re: Sure enough, the lock file is gone

From: "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Sure enough, the lock file is gone
Date: 2001-01-26 20:24:34
Message-ID: 20010126142434.A24790@rice.edu (view raw or flat)
Thread:
Lists: pgsql-hackers
On Fri, Jan 26, 2001 at 03:18:13PM -0500, Bruce Momjian wrote:
> > The 'tmpwatch' program on Red Hat will remove the /tmp/.s.PGSQL.5432.lock
> > file after the server has run 6 days.  This will be a problem.
> > 
> > We could touch (open) the file once every time the ServerLoop() runs
> > around.  It's not perfect but it should work in practice.
> 
> If we have to do it, let's make it an #ifdef __linux__ option.

#ifdef BRAINDAMAGED_TMP_CLEANER ?

ISTR mention of non-linux platforms that do this.

Ross

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2001-01-26 20:35:22
Subject: Re: This script will crash the connection
Previous:From: Bruce MomjianDate: 2001-01-26 20:18:13
Subject: Re: Sure enough, the lock file is gone

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