From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | emre(at)hasegeli(dot)com, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [PATCH] Improve geometric types |
Date: | 2018-09-03 00:52:28 |
Message-ID: | 58160ba3-6534-ba0f-b78f-d78b829db2d2@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 08/17/2018 11:23 PM, Tom Lane wrote:
> Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> writes:
>> Hmm, yeah. Based on past experience, the powerpc machines are likely to
>> stumble on this.
>
>> FWIW my understanding is that these failures actually happen in new
>> tests, it's not an issue introduced by this patch series.
>
> Yeah, we've definitely hit such problems before. The geometric logic
> seems particularly prone to it because it's doing more and subtler
> float arithmetic than the rest of the system ... but it's not the sole
> source of minus-zero issues.
>
It's not entirely clear to me what's the best way forward with this.
We can go through the patch and fix places with obvious -0 risks, but
then what? I don't have access to any powepc machines, so I can't check
if there are any other failures. So the only thing I could do is commit
and fix based on buildfarm failures ...
Emre, any better ideas?
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Hubert Zhang | 2018-09-03 01:49:22 | Re: Proposal for disk quota feature |
Previous Message | Tomas Vondra | 2018-09-03 00:35:00 | Re: memory leak when serializing TRUNCATE in reorderbuffer |