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 8456.980723199@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
List pgsql-hackers
teg@redhat.com (Trond Eivind Glomsrød) writes:
> 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".

> Between invocations of client programs. You're using /tmp as a shared
> of stored data.

Huh?  The socket and lockfile are created and held open by the
postmaster for the duration of its run.  Client programs don't even know
that the lockfile is there, in fact.  How can you argue that client
program lifespan has anything to do with it?
        regards, tom lane


pgsql-hackers by date:

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