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

From Michael Nolan
Subject Re: Ability to listen on two unix sockets
Date
Msg-id CAOzAquLMjvg6_gwsfbYwGLNWnODxN9aVbUDT6iPrYX5dS_f1hw@mail.gmail.com
Whole thread Raw
In response to Re: Ability to listen on two unix sockets  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Ability to listen on two unix sockets
List pgsql-hackers


On Mon, Jun 11, 2012 at 4:47 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
On sön, 2012-06-10 at 17:24 -0400, Robert Haas wrote:
> >> and also affects the naming of any UNIX sockets created.
> >
> > Why would that matter?  If you configure M ports and N Unix socket
> > locations, you get M*N actual sockets created.
>
> ...I *seriously* doubt that this is the behavior anyone wants.
> Creating M sockets per directory seems patently silly.

How else would it work?

If I say, syntax aside, listen on "ports" 5432 and 5433, and use socket
directories /tmp and /var/run/postgresql, then a libpq-using client
would expect to be able to connect using

-h /tmp -p 5432
-h /tmp -p 5433
-h /var/run/postgresql -p 5432
-h /var/run/postgresql -p 5433

So you do need to create M*N sockets.

I don't really see a problem with that.

What about entries in pg_hba.conf? Will they need to be able to specify both the directory and the port number?
--
Mike Nolan
 

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Ability to listen on two unix sockets
Next
From: Tom Lane
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Add ERROR msg for GLOBAL/LOCAL TEMP is not yet implemented