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

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

On Wed, Jan 29, 2014 at 12:02:37PM -0500, Paul Morie wrote:
> > Based on your setup, why would you not DNS-map "localhost" to whatever
> > 127.x.x.x address you gave that gear? We specifically bind to the
> > "localhost" string and not 127.0.0.1.
>
> The gears do not have their own DNS. Gear processes run in regular unix accounts
> and not in VMs, linux containers, etc.

I am guessing you can't use a Bind configuration file to return a
specific "localhost" IP address for specific gear because they don't
have unique IP source addresses, e.g. you can't filter the source
requests.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message craig.macdonald 2014-01-30 10:35:59 BUG #9038: trgm must have operand in index creation
Previous Message Marko Tiikkaja 2014-01-29 22:20:03 Re: BUG #8984: ERROR: t_xmin is uncommitted in tuple to be updated