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

From teg@redhat.com (Trond Eivind Glomsrød)
Subject Re: Re: Sure enough, the lock file is gone
Date
Msg-id xuysnm3xmx4.fsf@halden.devel.redhat.com
Whole thread Raw
In response to Re: Re: Sure enough, the lock file is gone  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> writes:

> 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?

Nothing but the postmaster uses it? If so, there shouldn't be a
problem moving it.

-- 
Trond Eivind Glomsrød
Red Hat, Inc.


pgsql-hackers by date:

Previous
From: Lamar Owen
Date:
Subject: Re: Re: Sure enough, the lock file is gone
Next
From: teg@redhat.com (Trond Eivind Glomsrød)
Date:
Subject: Re: Re: Sure enough, the lock file is gone