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 15945.1264695366@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 17:04, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I think what this shows is we should look for a way to avoid using
>> INADDR_NONE.

>> From some more googling
> (http://www.opengroup.org/onlinepubs/000095399/functions/inet_addr.html),
> it says it will return (in_addr_t)(-1), though, so maybe we should
> just move that #ifdef out to some global place?

Given the way that's written, I think we should just compare the result
to (in_addr_t)(-1), and not assume there's any macro provided for that.

However, now that I know the real issue is you're using inet_addr, I
would like to know why you're not using inet_aton instead; or even
better, something that also copes with IPv6.

            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: heikki@postgresql.org (Heikki Linnakangas)
Date:
Subject: pgsql: Fix crashing bug at the end of recovery in Streaming Replication,