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

Re: Sure enough, the lock file is gone

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>
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-27 04:52:51
Message-ID: 200101270452.XAA05187@candle.pha.pa.us (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.

Yes, thank you.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(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: 2001-01-27 04:55:16
Subject: Re: Sure enough, the lock file is gone
Previous:From: Bruce MomjianDate: 2001-01-27 04:43:00
Subject: Re: Hardwired MAXBACKENDS limit could be history

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