Re: Ability to listen on two unix sockets

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:59:37
Message-ID: 20120612215937.GF22649@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 12, 2012 at 05:48:58PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > On Wed, Jun 06, 2012 at 10:38:42AM -0400, Tom Lane wrote:
> >> 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?
>
> There's one socket for each entry in the listen_addresses list,
> plus one for the Unix socket.

Oh, how do we handle '*'? We pass that to the kernel, I assume. Shame
there is "wildcard" ability for unix domain sockets, which would use any
directory --- guess that wouldn't work out well. ;-)

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-06-12 22:02:48 Re: 9.3: load path to mitigate load penalty for checksums
Previous Message Jeff Davis 2012-06-12 21:55:30 Re: 9.3: load path to mitigate load penalty for checksums