From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Robert Young <yayooo(at)gmail(dot)com>, 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 15:00:54 |
Message-ID: | 23407.1319814054@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> 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.
The fundamental problem with that kluge (and yes, it's a kluge) is that
it supposes that you migrated EVERY local service to the other machine.
Which, obviously, you did not.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Young | 2011-10-28 15:16:37 | Re: Add statistics_collector_listen_addresses to fix hard-coding of "localhost" |
Previous Message | Robert Young | 2011-10-28 14:59:46 | Re: Add statistics_collector_listen_addresses to fix hard-coding of "localhost" |