PostgreSQL 8.1.5: regression tests fail on sparc

From: Дейтер Александр Валериевич <tiamat(at)komi(dot)mts(dot)ru>
To: pgsql-bugs(at)postgresql(dot)org
Subject: PostgreSQL 8.1.5: regression tests fail on sparc
Date: 2006-11-24 11:22:12
Message-ID: 4566D5E4.3020505@komi.mts.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

PostgreSQL 8.1.5 have a problem with division by zero on sparc.

Solaris 9 sparc, gcc 4.0.2, 4.1.1:

$ ./configure --enable-thread-safety --disable-nls --without-perl
--without-python --without-krb5 --without-openssl --without-readline
...
$ make && make check
...
=======================
1 of 98 tests failed.
=======================

The differences that caused some tests to fail can be viewed in the
file `./regression.diffs'. A copy of the test summary that you see
above is saved in the file `./regression.out'.

*** ./expected/errors.out Sat Feb 12 01:15:11 2005
--- ./results/errors.out Thu Nov 23 18:14:08 2006
***************
*** 300,308 ****
select 1/0::int8;
ERROR: division by zero
select 1::int2/0;
! ERROR: division by zero
select 1/0::int2;
! ERROR: division by zero
select 1::numeric/0;
ERROR: division by zero
select 1/0::numeric;
--- 300,310 ----
select 1/0::int8;
ERROR: division by zero
select 1::int2/0;
! ERROR: floating-point exception
! DETAIL: An invalid floating-point operation was signaled. This probably
means
an out-of-range result or an invalid operation, such as division by zero.
select 1/0::int2;
! ERROR: floating-point exception
! DETAIL: An invalid floating-point operation was signaled. This probably
means
an out-of-range result or an invalid operation, such as division by zero.
select 1::numeric/0;
ERROR: division by zero
select 1/0::numeric;

======================================================================

Thanks a lot!

--
Alex Deiter

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Sven Klemm 2006-11-24 18:35:44 BUG #2779: Making an inherited table to a view causes could not open relation error in base table
Previous Message Alex Deiter 2006-11-23 15:31:04 BUG #2778: make check failed