From: | Michael Nolan <htfoot(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Florian Pflug <fgp(at)phlo(dot)org>, Honza Horak <hhorak(at)redhat(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Ability to listen on two unix sockets |
Date: | 2012-06-11 23:45:13 |
Message-ID: | CAOzAquLMjvg6_gwsfbYwGLNWnODxN9aVbUDT6iPrYX5dS_f1hw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jun 11, 2012 at 4:47 PM, Peter Eisentraut <peter_e(at)gmx(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-06-11 23:45:20 | Re: Re: [COMMITTERS] pgsql: Add ERROR msg for GLOBAL/LOCAL TEMP is not yet implemented |
Previous Message | Tom Lane | 2012-06-11 22:07:34 | Re: Ability to listen on two unix sockets |