Re: listening addresses

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: listening addresses
Date: 2004-03-15 21:24:31
Message-ID: 40561F0F.1060809@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:

>Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>
>>The intention is to make "localhost" the default. That should translate
>>to 127.0.0.1 and ::1 (if they have ipv6 on). Of course, if they have a
>>broken resolver things might get sticky, but that is true now anyway.
>>
>>
>
>Just to be clear: right now, if "localhost" doesn't resolve then the
>stats collector will not start, but this doesn't prevent use of the
>database. It might be a good idea to ensure that the same is still true
>after making this change; that is, invalid entries in listen_addresses
>should only provoke warnings and not refusal to start (assuming that
>we are able to find at least one valid socket to listen to, of course).
>I believe that right now, any bad entry in virtual_host causes the
>postmaster to error out. That's defensible from one point of view but
>on balance I think it's overly paranoid. Any other opinions out there?
>
>
>

Makes sense - we are not giving anything away but *not* listening to
something.

I did wonder if we should treate "localhost" as a bit special and not
rely on the resolver for it.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-03-15 21:25:36 Re: WAL write of full pages
Previous Message Andrew Sullivan 2004-03-15 21:21:10 Re: The Name Game: postgresql.net vs. pgfoundry.org

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2004-03-15 22:13:34 Re: listening addresses
Previous Message Tom Lane 2004-03-15 20:54:38 Re: listening addresses