| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Florian Pflug <fgp(at)phlo(dot)org>, Honza Horak <hhorak(at)redhat(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Ability to listen on two unix sockets |
| Date: | 2012-06-12 21:39:39 |
| Message-ID: | 20120612213939.GD22649@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 06, 2012 at 10:38:42AM -0400, Tom Lane wrote:
> Florian Pflug <fgp(at)phlo(dot)org> writes:
> > Couldn't you simply tell postgres to put it's socket in, say, /var/run, and create a symlink to that socket in the global /tmp directory?
>
> FYI, this proposal emerged out of a discussion between Honza and
> myself. "Use a symlink" was my first idea too, but on reflection
> it seems like it will take less new code to support two sockets.
> We already support multiple TCP sockets, so multiple Unix sockets
---------------------------------------
> shouldn't be that much extra trouble.
We do? I didn't think listening on multiple interfaces meant we
listened on multiple sockets. Is there something else?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2012-06-12 21:40:11 | Re: 9.3: load path to mitigate load penalty for checksums |
| Previous Message | Tom Lane | 2012-06-12 21:38:33 | Re: Restrict ALTER FUNCTION CALLED ON NULL INPUT (was Re: Not quite a security hole: CREATE LANGUAGE for non-superusers) |