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

Re: pgsql: Define INADDR_NONE on Solaris when it's missing.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Define INADDR_NONE on Solaris when it's missing.
Date: 2010-01-28 16:04:37
Message-ID: 15704.1264694677@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Thu, Jan 28, 2010 at 16:46, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Magnus HaganderDate: 2010-01-28 16:09:35
Subject: Re: pgsql: Define INADDR_NONE on Solaris when it's missing.
Previous:From: Tim BunceDate: 2010-01-28 16:02:48
Subject: Re: Add on_perl_init and proper destruction to plperl [PATCH]

pgsql-committers by date

Next:From: Magnus HaganderDate: 2010-01-28 16:09:35
Subject: Re: pgsql: Define INADDR_NONE on Solaris when it's missing.
Previous:From: Magnus HaganderDate: 2010-01-28 15:53:44
Subject: Re: pgsql: Define INADDR_NONE on Solaris when it's missing.

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