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

From Magnus Hagander
Subject Re: pgsql: Define INADDR_NONE on Solaris when it's missing.
Date
Msg-id 9837222c1001281219n19384ae7k26fe0283395982e9@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Define INADDR_NONE on Solaris when it's missing.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
On Thu, Jan 28, 2010 at 21:16, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Magnus Hagander <magnus@hagander.net> writes:
>> On Thu, Jan 28, 2010 at 17:16, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> 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.
>
>> "Path of least resistance?"
>
>> Which method would you suggest?
>
> I haven't actually read the RADIUS patch, but generally we rely on
> pg_getaddrinfo_all to interpret strings representing IP addresses.
> Is there a reason not to use that?

I don't think so. I'll look it over.


--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Define INADDR_NONE on Solaris when it's missing.
Next
From: adunstan@postgresql.org (Andrew Dunstan)
Date:
Subject: pgsql: Fix bug found by warning from recent gcc.