| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Reini Urban <rurban(at)x-ray(dot)at> |
| Cc: | Adrian Maier <adrian(dot)maier(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: float8 regression failure (HEAD, cygwin) |
| Date: | 2006-07-20 14:54:44 |
| Message-ID: | 27320.1153407284@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Reini Urban <rurban(at)x-ray(dot)at> writes:
> BTW: HAVE_LONG_LONG_INT_64 is defined, so INT64_IS_BUSTED is defined also.
You sure? INT64_IS_BUSTED should *not* be set in that case --- it's
only supposed to be set if we couldn't find any 64-bit-int type at all.
As for the regression test failure, it's odd because it looks to me that
the actual test output is an exact match to the default "float8.out"
file. I'm not sure why pg_regress chose to report a diff against
float8-small-is-zero.out instead. This may be another teething pain
of the new pg_regress-in-C code --- could you trace through it and see
what's happening?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Saito | 2006-07-20 15:24:01 | Re: pg_regress breaks on msys |
| Previous Message | David Fetter | 2006-07-20 14:44:08 | Re: Units in postgresql.conf |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Saito | 2006-07-20 15:24:01 | Re: pg_regress breaks on msys |
| Previous Message | Tom Lane | 2006-07-20 14:32:47 | Re: pg_regress breaks on msys |