Re: Ability to listen on two unix sockets - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Ability to listen on two unix sockets
Date
Msg-id 20120612213939.GD22649@momjian.us
Whole thread Raw
In response to Re: Ability to listen on two unix sockets  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Ability to listen on two unix sockets
List pgsql-hackers
On Wed, Jun 06, 2012 at 10:38:42AM -0400, Tom Lane wrote:
> Florian Pflug <fgp@phlo.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@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Restrict ALTER FUNCTION CALLED ON NULL INPUT (was Re: Not quite a security hole: CREATE LANGUAGE for non-superusers)
Next
From: Jeff Davis
Date:
Subject: Re: 9.3: load path to mitigate load penalty for checksums