Known bugs in postgres95-1.0 for NEXTSTEP.

 ± We have been unable to test this release on HP-PA RISC and Sun Sparc platforms.

 ± Representation of floating point values on output, e.g. 2.999999999998 instead of 3.0. This is really a bug in NeXT's standard library so there is not much that we can do about it. (wait for NS 4.0 ±beg pardon, OpenStep for Mach± and hope it's fixed.  Yeah, sure;-). This error can also be seen on other RDBMS's whose backend runs on NEXTSTEP, e.g. Sybase.

 ± Floating point values that are too large or too small to be represented do not cause an overflow resp. underflow warning. -- this is, yet again, due to a NeXT standard library function that is not up to ANSI standards. Again, this can be seen with other environments too.

 ± Some inconsistencies in behaviour between the Intel and NeXT versions of postgres95 showed in the regression test, that we were unable to track down.  In general, the Intel version is somewhat closer to the ``canonical'' behaviour than the NeXT version.

 ± A bug in the dynamic loader error handling causes a crash of the postgres95 backend when an attempt to load an object file of the wrong architecture is made.

R&A  -- 1996/02/24