From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Huong Dangminh <huo-dangminh(at)ys(dot)jp(dot)nec(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Akio Iwaasa <aki-iwaasa(at)vt(dot)jp(dot)nec(dot)com> |
Subject: | Re: power() function in Windows: "value out of range: underflow" |
Date: | 2018-05-01 17:38:44 |
Message-ID: | CA+TgmoYy5LHbWt8gfOgnHBvt_3NTs-2xbyD6unDpGYxkQKtzhw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Sun, Apr 29, 2018 at 7:24 PM, David Rowley
<david(dot)rowley(at)2ndquadrant(dot)com> wrote:
> I think we should back patch and try to be consistent about the
> power(float8 1.0, 'NaN') and power('NaN', float8 0.0) cases. The
> archives don't show any complaints about power() with NaN until this
> one, so I imagine the number of people affected by this is small.
I agree that this is not likely to affect a lot of people -- but the
question isn't how many people will be affected but rather, of those
that are, how many of them will be pleased rather than displeased by a
change. I would argue that the results have to be unambiguously wrong
in the back-branches to justify a change there, and this doesn't
appear to meet that standard. I would guess that the number of people
who use NaN is very small, but those people have probably adapted
their application to the behavior they are getting currently.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-05-01 17:49:18 | Re: power() function in Windows: "value out of range: underflow" |
Previous Message | David G. Johnston | 2018-05-01 16:39:22 | Re: Usage of pg_waldump |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2018-05-01 17:41:32 | Re: Oddity in tuple routing for foreign partitions |
Previous Message | Robert Haas | 2018-05-01 17:21:21 | Re: Fsync request queue |