From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Ability to listen on two unix sockets |
Date: | 2012-06-09 22:25:30 |
Message-ID: | 201206100025.31297.andres@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sunday, June 10, 2012 12:09:30 AM Peter Eisentraut wrote:
> On lör, 2012-06-09 at 23:45 +0200, Andres Freund wrote:
> > On Saturday, June 09, 2012 11:43:53 PM Peter Eisentraut wrote:
> > > On ons, 2012-06-06 at 11:21 -0400, Tom Lane wrote:
> > > > I'm not really in favor of making /var/run be the out-of-the-box
> > > > default, because it would discriminate against personal/testing
> > > > installations (ie, you couldn't set it up without root privileges).
> > > > It's a reasonable choice for distro-provided packages, but not so
> > > > much for one-off builds --- think about the buildfarm if nothing
> > > > else.
> > > >
> > > > Having said that, if we made it easier to configure things that way
> > > > than by patching the source, I bet Martin Pitt isn't going to object.
> > >
> > > 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.
> > That doesn't help libpq using clients.
> There is no mandate here to do anything about that.
Well, Martin Pitt/the debian package is patching exactly that. Youre saying
that everything that needs to be done to make that easier is to make
unix_socket_dir a list. So there seems to be some disparity there ;)
Andres
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-06-09 22:26:21 | Re: Ability to listen on two unix sockets |
Previous Message | Peter Eisentraut | 2012-06-09 22:12:39 | Re: Ability to listen on two unix sockets |