Re: Add statistics_collector_listen_addresses to fix hard-coding of "localhost" - Mailing list pgsql-bugs

From Robert Young
Subject Re: Add statistics_collector_listen_addresses to fix hard-coding of "localhost"
Date
Msg-id CAJjz_Niz1WOzcenFBiAbzfFM1k_cEOuOF3YhTRVa79ijveNOtQ@mail.gmail.com
Whole thread Raw
In response to Re: Add statistics_collector_listen_addresses to fix hard-coding of "localhost"  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-bugs
Don't be so surprised, because the app just as same as PG hard-coding
"localhost".

On Fri, Oct 28, 2011 at 14:54, Alvaro Herrera
<alvherre@commandprompt.com> wrote:
>
> Excerpts from Robert Young's message of vie oct 28 11:47:14 -0300 2011:
>>
>> I just migrate some services from one machine to another but database
>> stay there.
>> So, I think the most simple solution is to change =E2=80=9Clocalhost=E2=
=80=9D point to
>> the new one, so that I need no modification of client applications.
>> But found PG gave warnings.
>
> I'm surprised that your conclusion was that the path of least resistance
> was submitting a patch to Postgres. =C2=A0Surely patching the apps would =
have
> been a lot easier.
>
> --
> =C3=81lvaro Herrera <alvherre@commandprompt.com>
> The PostgreSQL Company - Command Prompt, Inc.
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
>

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Add statistics_collector_listen_addresses to fix hard-coding of "localhost"
Next
From: Tom Lane
Date:
Subject: Re: Add statistics_collector_listen_addresses to fix hard-coding of "localhost"