Re: duplicate connection failure messages - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: duplicate connection failure messages
Date
Msg-id 201011202043.oAKKhTs01861@momjian.us
Whole thread Raw
In response to Re: duplicate connection failure messages  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: duplicate connection failure messages
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > I was wondering that.  I am unclear if we need it though --- can we not
> > assume inet_ntop() exists on all systems?  We assumed inet_ntoa() did. 
> 
> The Single Unix Spec includes inet_ntoa but not inet_ntop.
> 
> > Of course, the buildfarm will tell us.
> 
> The buildfarm unfortunately contains only a subset of the platforms
> we care about.  I don't think this problem is large enough to justify
> taking a portability risk by depending on non-SUS library functions.
> 
> If you want to do this, please do it as suggested previously, ie depend
> on the copy of the code we have internally.

I assume you are suggesting to use our inet_net_ntop() even if the
system has inet_ntop().

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] Custom code int(32|64) => text conversions out of performance reasons
Next
From: Tom Lane
Date:
Subject: Re: Fwd: What do these terms mean in the SOURCE CODE?