Re: BUG #9003: Hard-coding to localhost in postmaster

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Paul Morie <pmorie(at)redhat(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #9003: Hard-coding to localhost in postmaster
Date: 2014-01-28 16:15:54
Message-ID: 23411.1390925754@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> On 2014-01-28 10:41:49 -0500, Paul Morie wrote:
>> The challenge we have in openshift is that we have multiple users on a
>> single node who all want to bind to the same port. To deal with this,
>> we forbid the users from binding to 127.0.0.1 using selinux and
>> allocate IPs for them to bind to.

> Uhm. What about using network namespaces?

> To me this really sounds like tackling things from the wrong
> end. Instead of fixing the infrastructure once this way you need to
> adapt various pieces of software in odd ways.

Yeah. In particular, I'd always supposed that a platform that wanted
to use some other IP address than 127.0.0.1 for loopback would also be
expected to make sure that "localhost" mapped to that other IP address.
Otherwise, there simply isn't any way to make network-using software
work except random hacks.

Frankly, I don't think you're going to get any cooperation from Postgres
in adapting to such a broken networking environment as this, and I doubt
other upstreams are going to be any more positive about it.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2014-01-28 16:19:00 Re: BUG #9003: Hard-coding to localhost in postmaster
Previous Message Andres Freund 2014-01-28 15:54:19 Re: BUG #9003: Hard-coding to localhost in postmaster