Re: [HACKERS] flock patch breaks things here
От | The Hermit Hacker |
---|---|
Тема | Re: [HACKERS] flock patch breaks things here |
Дата | |
Msg-id | Pine.BSF.4.05.9810301616220.1918-100000@thelab.hub.org обсуждение исходный текст |
Ответ на | Re: [HACKERS] flock patch breaks things here (Bruce Momjian <maillist@candle.pha.pa.us>) |
Список | pgsql-hackers |
On Fri, 30 Oct 1998, Bruce Momjian wrote: > > 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. > > Just a reminder that if you move it, all clients must know the new > location, or somehow the location must be accessable by the clients. Which is only relevant if using Unix-domain sockets... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
В списке pgsql-hackers по дате отправления: