Re: host name support in pg_hba.conf

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>, pgsql-hackers(at)postgresql(dot)org, Steve Atkins <steve(at)blighty(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: host name support in pg_hba.conf
Date: 2010-10-06 20:09:55
Message-ID: AANLkTikXVAyv5XUhPqxzsNO7czUz+m2i7hqhLT09aYe+@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 6, 2010 at 6:21 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> It's not common, but i've certainly come across a number of virtual
> machines where localhost resolves (through /etc/hosts) to the machines
> "real" IP rather than 127.0.01, because 127.0.0.1 simply doesn't
> exist.

It's perfectly fine for localhost to resolve to the machine's external
ip address. It would be weird for it to resolve to some other host's
ip address like the vm's host machine. But having 127.0.0.1 not exist
would be positively broken. All kinds of things wouldn't work. Are you
sure about that part?

--
greg

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-10-06 21:02:22 Re: security hook on table creation
Previous Message Simon Riggs 2010-10-06 20:01:13 Re: Issues with Quorum Commit