Re: [HACKERS] [COMMITTERS] pgsql: Work around reported problem that AIX's getaddrinfo() doesn't

2006-10-19 Thread Rocco Altier
This change has broken my AIX 5.2 buildfarm machine (asp/kookaburra),
but doesn't seem to break the 5.3 member (grebe).

It appears to have problems with stats being off now?

What can I do to help debug the situation?

-rocco

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
 Sent: Thursday, October 19, 2006 1:27 PM
 To: pgsql-committers@postgresql.org
 Subject: [COMMITTERS] pgsql: Work around reported problem 
 that AIX's getaddrinfo() doesn't 
 
 
 Log Message:
 ---
 Work around reported problem that AIX's getaddrinfo() doesn't 
 seem to zero
 sin_port in the returned IP address struct when servname is 
 NULL.  This has
 been observed to cause failure to bind the stats collection 
 socket, and
 could perhaps cause other issues too.  Per reports from Brad Nicholson
 and Chris Browne.
 
 Modified Files:
 --
 pgsql/src/backend/libpq:
 ip.c (r1.36 - r1.37)
 
 (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/
libpq/ip.c.diff?r1=1.36r2=1.37)

---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
   subscribe-nomail command to [EMAIL PROTECTED] so that your
   message can get through to the mailing list cleanly

---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings


Re: [HACKERS] [COMMITTERS] pgsql: Work around reported problem that AIX's getaddrinfo() doesn't

2006-10-19 Thread Tom Lane
Rocco Altier [EMAIL PROTECTED] writes:
 This change has broken my AIX 5.2 buildfarm machine (asp/kookaburra),
 but doesn't seem to break the 5.3 member (grebe).

Sigh, count on IBM to make life complicated.

Instead of hacking servname, I suppose we will have to poke the correct
value into sin_port afterwards.  Would you check on the names of the
port fields in the IPv4 and IPv6 cases?  (It might be s6_port or some
such for IPv6.)

regards, tom lane

---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
   subscribe-nomail command to [EMAIL PROTECTED] so that your
   message can get through to the mailing list cleanly