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

From Tom Lane
Subject Re: Ability to listen on two unix sockets
Date
Msg-id 5104.1339279364@sss.pgh.pa.us
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  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.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?

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.  But we could add a run-time-configured list
of secondary directories to establish sockets in.
        regards, tom lane


pgsql-hackers by date:

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