> It would probably be better if the socket files weren't in /tmp but in
> a postgres-owned directory. However, at this point we have a huge
> backwards compatibility problem to overcome if we want to move the
> socket files. The location of the socket files is essentially a core
> part of the frontend-backend protocol, because both client and server
> must know it ab initio. Move the socket, break your clients.
Ok, fair enough.
But sometimes unix sucks, don't you think, having to use /tmp as a
central place for inter-process communication... blech.
Florent
--
<florent.guillaume@mail.com>