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

From: Robert Young <yayooo(at)gmail(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, robertmhaas(at)gmail(dot)com, 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 16:18:37
Message-ID: CAJjz_Nju=D3Y5VqOs+-abKU4vFQTaLoG-Kyb0eZw8H5U_4xJAw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

You got no knowledge about "client applications".
What you said is your assumption.
Without knowledge, you should consider them equivalent.
PG got no priority.

On Fri, Oct 28, 2011 at 16:03, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> On 28.10.2011 18:40, Robert Young wrote:
>>
>> Which wrong?
>> 1.I got no money to buy a good machine to run both the services and
>> database.
>> 2.I got no money to buy a good machine to run both the services and
>> client applications.
>> 3.Client applications hard-coding "localhost".
>> 4.PG hard-coding "localhost".
>
> #3. Fix the applications to not hard-code "localhost". The difference
> between #3 and #4 is that PostgreSQL really genuinely always does mean to
> connect to the local host, while #3 actually wants to connect to some other
> host, but it was not made configurable.
>
> --
>  Heikki Linnakangas
>  EnterpriseDB   http://www.enterprisedb.com
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message John R Pierce 2011-10-28 16:24:58 Re: Add statistics_collector_listen_addresses to fix hard-coding of "localhost"
Previous Message Heikki Linnakangas 2011-10-28 16:03:46 Re: Add statistics_collector_listen_addresses to fix hard-coding of "localhost"