Re: Re: Sure enough, the lock file is gone
От | teg@redhat.com (Trond Eivind Glomsrød) |
---|---|
Тема | Re: Re: Sure enough, the lock file is gone |
Дата | |
Msg-id | xuysnm3xmx4.fsf@halden.devel.redhat.com обсуждение исходный текст |
Ответ на | Re: Re: Sure enough, the lock file is gone (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | 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 по дате отправления: