Re: listening addresses - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: listening addresses
Date
Msg-id 40561F0F.1060809@dunslane.net
Whole thread Raw
In response to Re: listening addresses  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: listening addresses  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:

>Andrew Dunstan <andrew@dunslane.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


pgsql-hackers by date:

Previous
From: Andrew Sullivan
Date:
Subject: Re: The Name Game: postgresql.net vs. pgfoundry.org
Next
From: Tom Lane
Date:
Subject: Re: WAL write of full pages