From: | Robert Young <yayooo(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, GavinFlower <gavinflower(at)archidevsys(dot)co(dot)nz>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: Add statistics_collector_listen_addresses to fix hard-coding of "localhost" |
Date: | 2011-10-28 14:59:46 |
Message-ID: | CAJjz_Niz1WOzcenFBiAbzfFM1k_cEOuOF3YhTRVa79ijveNOtQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)commandprompt(dot)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 “localhost” 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. Surely patching the apps would have
> been a lot easier.
>
> --
> Álvaro Herrera <alvherre(at)commandprompt(dot)com>
> The PostgreSQL Company - Command Prompt, Inc.
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-10-28 15:00:54 | Re: Add statistics_collector_listen_addresses to fix hard-coding of "localhost" |
Previous Message | Alvaro Herrera | 2011-10-28 14:54:00 | Re: Add statistics_collector_listen_addresses to fix hard-coding of "localhost" |