From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: mingw32 floating point diff |
Date: | 2019-08-23 12:25:01 |
Message-ID: | bd2123c3-cd02-206d-0adb-2f65b5aeac01@2ndQuadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 8/20/19 8:59 AM, Peter Eisentraut wrote:
> Running the regression tests on mingw32, I get the following diff in
> circle.out:
>
> @@ -111,8 +111,8 @@
> WHERE (c1.f1 < c2.f1) AND ((c1.f1 <-> c2.f1) > 0)
> ORDER BY distance, area(c1.f1), area(c2.f1);
> five | one | two | distance
> -------+----------------+----------------+------------------
> - | <(3,5),0> | <(1,2),3> | 0.60555127546399
> +------+----------------+----------------+-------------------
> + | <(3,5),0> | <(1,2),3> | 0.605551275463989
> | <(3,5),0> | <(5,1),3> | 1.47213595499958
> | <(100,200),10> | <(100,1),115> | 74
> | <(100,200),10> | <(1,2),100> | 111.370729772479
>
> I only get this on master/PG12, but not on PG11, so I suspect that the
> new floating-point output routines could be the root of the issue.
>
> This happens only with the 32-bit build (mingw32), but not with a 64-bit
> build (mingw64).
>
> Any suggestions on how to analyze this further?
>
I complained about this a year ago:
<https://postgr.es/m/9f4f22be-f9f1-b350-bc06-521226b87f7a@dunslane.net>
+1 for fixing it by any reasonable means.
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Pierre Giraud | 2019-08-23 12:47:56 | Explain: Duplicate key "Workers" in JSON format |
Previous Message | Asim R P | 2019-08-23 12:09:35 | Re: Cleanup isolation specs from unused steps |