Re: [HACKERS] flock patch breaks things here
| От | Tom Lane |
|---|---|
| Тема | Re: [HACKERS] flock patch breaks things here |
| Дата | |
| Msg-id | 17577.909721036@sss.pgh.pa.us обсуждение |
| Ответ на | Re: [HACKERS] flock patch breaks things here (The Hermit Hacker <scrappy@hub.org>) |
| Ответы |
Re: [HACKERS] flock patch breaks things here
Re: [HACKERS] flock patch breaks things here |
| Список | pgsql-hackers |
The Hermit Hacker <scrappy@hub.org> writes:
> On Sun, 30 Aug 1998, Tom Lane wrote:
>> So I think I have to vote in favor of leaving the socket where it is.
> Let me put my vote in...: $PGSQLHOME/run/{pgsql.pid,pgsql.pid.socket}
> Screw backwards compatibility...v6.5 becomes v7.0 *shrug*
Catching up on back email, Marc?
I think the end consensus of that thread was that we should move the
socket file to someplace safer than /tmp (exactly where being a
configure-time choice), *and* optionally put a softlink to it in /tmp
for backwards compatibility with old clients. Use of the /tmp link
would be deprecated because of possible security risks, but it could
continue to work for as long as a particular installation needed to
keep that option enabled.
Actually getting it done doesn't seem to have happened :-(. I think
we were all viewing this as part & parcel of fixing the lockfile issues,
which no one got exercised enough to do. Too many higher-priority
tasks...
regards, tom lane
В списке pgsql-hackers по дате отправления: