After rebuilding and retesting from a CVS update last night, I can
report that all tests passed with the following exceptions:

float8 has some problems with very large and very small numbers.
datetime and horology have some problems with 'current' and 'epoch'
   which might (or might not) be related to the float8 problems.

I am quite impressed.  Because of all of your work, I can do my
semester database project at home in PostgreSQL rather than on the
schools (extremely poorly managed) network and (OK as far as I can
tell) Oracle system.

Thanks much.  I'll have more diffs when I figure out the problems.
Maybe for 6.4.1, maybe for 6.5 kinda depends on the bugs, and my
time, and how much that baby due on Jan 2 is going to keep me awake
at night 8-).  (Our first one was really really bad about that for
a few months.)

Jon

Fri, 30 Oct 1998 10:59:21 -0600
Jon Buller <jonb@metronet.com>
NetBSD/NS32K regression results
Jon Buller <jonb@metronet.com> writes:
> After rebuilding and retesting from a CVS update last night, I can
> report that all tests passed with the following exceptions:

Great!

> float8 has some problems with very large and very small numbers.
> datetime and horology have some problems with 'current' and 'epoch'
>    which might (or might not) be related to the float8 problems.

I think you guessed right.  IIRC, datetime has an underlying
representation of float8, and some of the special values like
"current" are represented as particular very-large or very-small
numbers.  So it might break if your machine's float math is not
up to IEEE-float specs.  However, you can do an awful lot of stuff
with datetime without ever needing the special values, so this
might not be much of a problem for you.

			regards, tom lane

Fri, 30 Oct 1998 16:43:58 -0500
Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] NetBSD/NS32K regression results 