Skip site navigation (1) Skip section navigation (2)

Re: Ability to listen on two unix sockets

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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-09 22:12:39
Message-ID: 1339279959.5751.24.camel@vanquo.pezone.net (view raw or flat)
Thread:
Lists: pgsql-hackers
On lör, 2012-06-09 at 18:02 -0400, Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > We already have the ability to configure the Unix socket directory in
> > postgresql.conf.  All you need to do is turn that into a list.
> 
> Um, no, it's not quite that simple.  In particular, what do you think
> should happen on the client side?

Nothing changes there.

> I'm inclined to think that we should (continue to) have a hardwired
> "primary" directory, which is the one that libpq is also configured
> to look in by default.

Yes.

> But we could add a run-time-configured list of secondary directories to establish sockets in.

Yes, I'm just pointing out that we already have that list
(unix_socket_directory in postgresql.conf), except it's currently
limited to length 1, because no one has needed a longer one until now.


In response to

Responses

pgsql-hackers by date

Next:From: Andres FreundDate: 2012-06-09 22:25:30
Subject: Re: Ability to listen on two unix sockets
Previous:From: Peter EisentrautDate: 2012-06-09 22:09:30
Subject: Re: Ability to listen on two unix sockets

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group