Re: Re: Sure enough, the lock file is gone - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: Sure enough, the lock file is gone
Date
Msg-id 4918.980722043@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: Sure enough, the lock file is gone  (teg@redhat.com (Trond Eivind Glomsrød))
Responses Re: Re: Sure enough, the lock file is gone  (teg@redhat.com (Trond Eivind Glomsrød))
List pgsql-hackers
teg@redhat.com (Trond Eivind Glomsrød) writes:
> Ideally, the locks should be in /var/lock/pgsql and the socket
> somewhere else - like /var/lib/pgsql (our mysql packages do this, and
> both of them are specified in /etc/my.cnf).

That is not "ideal", in fact it would break one of the specific features
that UUNET asked us for.  Namely, to be able to have noninterfering
sets of socket files in different explicitly-specified directories.
If the lock files don't live where the sockets do, then this doesn't work.

> Explictly, yes. However, FHS says /tmp is for temporary files. Also,
> it says programs shouldn't count on data to be stored there between
> invocations. 10+ days isn't temporary...

We aren't counting on data to be stored in /tmp "between invocations".
The socket and lock file live only as long as the postmaster runs.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Lamar Owen
Date:
Subject: Re: Re: Sure enough, the lock file is gone
Next
From: Tom Lane
Date:
Subject: Re: Re: Sure enough, the lock file is gone