Re: pgsql: Define INADDR_NONE on Solaris when it's missing. - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Define INADDR_NONE on Solaris when it's missing.
Date
Msg-id 15704.1264694677@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Define INADDR_NONE on Solaris when it's missing.  (Magnus Hagander <magnus@hagander.net>)
Responses Re: pgsql: Define INADDR_NONE on Solaris when it's missing.
List pgsql-committers
Magnus Hagander <magnus@hagander.net> writes:
> On Thu, Jan 28, 2010 at 16:46, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Possibly more to the point, where are we using INADDR_NONE anyway?

> In the RADIUS code.

Oh, that's why it isn't in my tree and has zero portability track record ...

I think what this shows is we should look for a way to avoid using
INADDR_NONE.  What's your grounds for believing it's portable at all?
In the Single Unix Spec I only see INADDR_ANY and INADDR_BROADCAST
defined.

            regards, tom lane

pgsql-committers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: pgsql: Define INADDR_NONE on Solaris when it's missing.
Next
From: Magnus Hagander
Date:
Subject: Re: pgsql: Define INADDR_NONE on Solaris when it's missing.