From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Do we always need the socket file? |
Date: | 2003-02-14 18:19:50 |
Message-ID: | 878ywiiv21.fsf@stark.dyndns.tv |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Michael Brusser <michael(at)synchronicity(dot)com> writes:
> We're trying to avoid creating any unnecessary files, especially outside
> of the product installation tree. Look at this as a policy.
> Experience shows that sooner or later some of your customers ask you:
> what is this /tmp/.s.PGSQL.xxx file is? What do I need it for?
> Also some admins known to periodically clean out /tmp, /var/run, etc.
Well if you clean out files programs are using you should expect those
programs to break. Other programs that create sockets in /tmp include screen
and X for example.
Unix domain sockets are sometimes more efficient and sometimes more secure
than TCP/IP connections. So preferring TCP/IP just to avoid /tmp pollution
might be a bit of a loss for aesthetic value.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Wolff III | 2003-02-14 18:27:49 | Re: location of the configuration files |
Previous Message | Greg Stark | 2003-02-14 18:16:26 | Re: location of the configuration files |