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

From: Paul Morie <pmorie(at)redhat(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #9003: Hard-coding to localhost in postmaster
Date: 2014-01-28 00:06:21
Message-ID: 1274922501.13409952.1390867581243.JavaMail.root@redhat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Andres-

The specific use-case I'm trying to address is within OpenShift (www.openshift.com) where users cannot bind to localhost of 127.0.0.1. In this case, the user needs to be able to bind to another interface.

P

----- Original Message -----
> From: "Andres Freund" <andres(at)2ndquadrant(dot)com>
> To: pmorie(at)redhat(dot)com
> Cc: pgsql-bugs(at)postgresql(dot)org
> Sent: Monday, January 27, 2014 6:20:50 PM
> Subject: Re: [BUGS] BUG #9003: Hard-coding to localhost in postmaster
>
> On 2014-01-27 18:31:25 +0000, pmorie(at)redhat(dot)com wrote:
> > The following bug has been logged on the website:
> >
> > Bug reference: 9003
> > Logged by: Paul Morie
> > Email address: pmorie(at)redhat(dot)com
> > PostgreSQL version: 9.2.4
> > Operating system: RHEL
> > Description:
> >
> > Currently there is a hard-coding in postgresql postmaster to bind to
> > 'localhost'. This results in postmaster and autovacuum being broken if the
> > user cannot bind to 127.0.0.1.
>
> Why would the user be unable to bind to 127.0.0.1? I.e. what's the
> usecase this would allow?
>
> Greetings,
>
> Andres Freund
>
> --
> Andres Freund http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message martin.nzioki 2014-01-28 00:08:40 BUG #9006: Incorrect update when using where with non-existent column in subselect
Previous Message Tom Lane 2014-01-28 00:00:52 Re: BUG #9003: Hard-coding to localhost in postmaster