Re: Re: Sure enough, the lock file is gone

> It has touched a nerve, hasn't it?  I like your solution -- but, to
> reiterate, this IMHO is 7.2 material, unless we want to go the feature
> patch route, or someone considers this a 'bugfix' (I don't).  Unless it
> is a trivial change, that is.
> 
> Tom fixed the bug with a slight kludge -- by touching the lock
> periodically, the problem is ameliorated for now.  But as long as we
> have a persistent file in /tmp we will run into OS-dependent problems. 
> I can see now a bug report that PostgreSQL is unreliable because it
> keeps crashing every x days (due to a tmpreaper-like program the hapless
> user doesn't know is running in cron....).
> 
> Since pg_config already reports what configure options were provided, if
> this is a configure option then the end user can easily find it with
> pg_config, if a static linkage or binary-only custom client that
> directly accesses the fe-be protocol (are there any that we know
> about?).

No one has suggested a location non-root people can put the socket/lock
file, except /tmp, and IMHO, until we find one, the default stays in
/tmp.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026