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: | 20010129104352.B690@rice.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
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
> BRAINDAMAGED_TMP_CLEANER though.
>
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.
Ross
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-01-29 16:44:39 | Re: Shouldn't this be an error? |
Previous Message | Bruce Momjian | 2001-01-29 16:37:19 | Re: BLOB HOWTO?? |