Larry Rosenman <[EMAIL PROTECTED]> writes:
> *** ./expected/union.out Thu Oct 9 20:49:31 2003
> --- ./results/union.out Fri Oct 31 15:15:50 2003
> ***************
> *** 106,112 ****
> two
> -----
> 1.1
> ! 2
> (2 rows)
> SELECT 1.1 AS three UNION SELECT 2 UNION ALL SELECT 2;
> --- 106,112 ----
> two
> -----
> 1.1
> ! 2.0
> (2 rows)
I think this is just a platform-specific difference in the behavior of
qsort(). Numeric "2" and "2.0" print differently, but they are equal
according to the comparison operators, so it's mostly luck of the draw
which one is selected for output.
The original coding of this regression test expected that these values
would be interpreted as float8, wherein there is no difference between
"2" and "2.0". I'm kind of inclined to change the test back to using
float8 so we don't see more of these reports.
> *** ./expected/join.out Thu Oct 9 20:49:31 2003
> --- ./results/join.out Fri Oct 31 15:15:51 2003
> [ row ordering differences ]
This also looks like platform-specific behavior --- the differences are
in the sort ordering of rows with equal keys.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
