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: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Sure enough, the lock file is gone
Date: 2001-01-29 16:43:52
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Fri, Jan 26, 2001 at 11:55:16PM -0500, Bruce Momjian wrote:
> > I said:
> > > Yes, there are lots of systems that will clean /tmp --- and since the
> > > lock file is an ordinary file (not a socket) pretty much any tmp-cleaner
> > > is going to decide to remove it.  I think that I had intended to insert
> > > a periodic touch of the lockfile and forgot to.
> > 
> > Done now.
> Yes, checkpoint is a good place to put it.  Thanks.  I still liked the

Well, from reading the rest of the thread, it seems that, while tmpreaper
_is_, in fact, brain damaged (it'll eat socket files) that wasn't what we
were talking about: removal of apparently stale ordinary files, like our
lockfile, is what tmp cleaners are all about, even if it is problematic.

Personally, I've always thought tmp cleaners are a bad idea, a bandaid
approach to cleaning up after poorly written software: i.e. broken by
design. Well, it's resolved now, for pgsql. Can't fix all the software
out there, I guess.


In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2001-01-29 16:44:39
Subject: Re: Shouldn't this be an error?
Previous:From: Bruce MomjianDate: 2001-01-29 16:37:19
Subject: Re: BLOB HOWTO??

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