From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Postgresql Dev <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Tru64/Alpha problems |
Date: | 2006-03-28 15:24:55 |
Message-ID: | 1914.1143559495@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Honda Shigehiro has diagnosed the longstanding problems with his
> Tru64/Alpha buildfarm member (bear). See below.
> First, it appears that there is a problem with the system getaddrinfo(),
> which configure reports as usable, but turns out not to be. Our current
> configure test checks the return value of getaddrinfo("", "", NULL,
> NULL) but I am wondering if we should test for "localhost" instead of ""
> as the first parameter.
Huh? That's just an AC_TRY_LINK test, we don't actually execute it.
If we did, the test would fail on machines where resolution of "localhost"
is broken, which we already know is a not-so-rare disease ...
I'm not sure that I believe the "getaddrinfo doesn't work" diagnosis
anyway, seeing that bear gets through "make check" okay. Wouldn't that
fail too if there were a problem there?
> Second, it appears that this platform apparently doesn't handle Infinity
> and NaN well. The regression diffs are attached.
On the FPE front, it'd be useful to get a gdb traceback to see where the
SIGFPE is occurring.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-03-28 15:36:38 | Re: Tablespaces oddity? |
Previous Message | Tom Lane | 2006-03-28 15:07:35 | Re: [GENERAL] PANIC: heap_update_redo: no block |