Re: Add statistics_collector_listen_addresses to fix hard-coding of "localhost"

From: Robert Young <yayooo(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Add statistics_collector_listen_addresses to fix hard-coding of "localhost"
Date: 2011-11-09 15:18:00
Message-ID: CAJjz_NiGct3iLipCk9JC2TY5u+u9A0CzvH64zys+V=nYSG-zUw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Yes,PG told me about this:

LOG: could not resolve "localhost": no address associated with name
LOG: disabling statistics collector for lack of working socket
WARNING: autovacuum not started because of misconfiguration
HINT: Enable the "track_counts" option.
LOG: database system was shut down at 2011-10-27 09:43:18 GMT
LOG: database system is ready to accept connections

On Wed, Nov 9, 2011 at 15:06, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Andres Freund wrote:
>> Hi Robert,
>>
>> On Thursday, October 27, 2011 12:38:02 PM Robert Young wrote:
>> > What Would Happen if I got NO "localhost" entry in my /etc/hosts ?
>> Why should pg cater for such a broken configuration? Sorry for being harsh but
>> that seems like it would end in heaps of workarounds.
>
> Do we throw at least a log message warning if localhost isn't resolved?
> If not, we should.  (I don't want to break my OS to test this.)
>
> --
>  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
>  EnterpriseDB                             http://enterprisedb.com
>
>  + It's impossible for everything to be true. +
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2011-11-09 16:48:33 Re: Add statistics_collector_listen_addresses to fix hard-coding of "localhost"
Previous Message Bruce Momjian 2011-11-09 15:06:01 Re: Add statistics_collector_listen_addresses to fix hard-coding of "localhost"