Skip site navigation (1) Skip section navigation (2)

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Robert Young <yayooo(at)gmail(dot)com>, 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-10-27 14:42:16
Message-ID: 28326.1319726536@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> BTW, do we have anything in place to stop any user on the same host to 
> send bogus stat messages to the stats collector?

Yes.  Use of the connect() call is supposed to guarantee that we will
only receive packets originating from our own socket address.

As far as the original topic goes, I agree that it seems rather
pointless to worry about systems that fail to resolve "localhost".
Doing so is required by relevant RFCs, eg 
http://www.faqs.org/rfcs/bcp/bcp32.html
(That's probably not the only one, it's just the first hit I found
while searching the RFC archives.)

And, given that we've been doing it this way since 2001 without
previous complaints, the number of systems that fail to do it
must be pretty small.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Jan-Peter SeifertDate: 2011-10-27 15:23:41
Subject: BUG #6274: documentation on pg_attribute.atttypmod
Previous:From: JustinDate: 2011-10-27 13:46:17
Subject: BUG #6273: Install Error

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group