On Sun, May 13, 2018 at 05:43:25PM +0900, Đặng Minh Hướng wrote:
> Hello Bruce,
>
> Thanks for the greate work!
>
> 2018-05-12 0:08 GMT+09:00 Bruce Momjian <br...@momjian.us>:
>
> I have committed the first draft of the Postgres 11 release notes. I
> will add more markup soon. You can view the most current version here:
>
> http://momjian.us/pgsql_docs/release-11.html
>
> I expect a torrent of feedback. ;-)
>
>
> I think the behavior change (from PostgreSQL 11) of power() with NaN below
> also
> need to report to users as the major change.
>
> related commit: 61b200e2f582d0886d9de947e182483339d881fd
> 6bdf1303b34bc630e8945ae3407ec7e8395c8fe5
>
> Discussion: https://postgr.es/m/
> 75db81beea95b445ae6d576a0a5c9e936a73e...@bpxm05gp.gisp.nec.co.jp
Wow, that is an interesting case. The patch was applied to head and
backbranches, (so I didn't see it) but three days later reverted in back
branches, and after my date cut-off:
commit f74d83b3034f830bd68489b4aba99a4dee29c565
Author: Tom Lane <t...@sss.pgh.pa.us>
Date: Wed May 2 17:32:40 2018 -0400
Revert back-branch changes in power()'s behavior for NaN inputs.
Per discussion, the value of fixing these bugs in the back branches
doesn't outweigh the downsides of changing corner-case behavior in
a minor release. Hence, revert commits 217d8f3a1 and 4d864de48 in
the v10 branch and the corresponding commits in 9.3-9.6.
Discussion:
https://postgr.es/m/75db81beea95b445ae6d576a0a5c9e936a73e...@bpxm05gp.gisp.nec.co.jp
Added:
Consistently return <literal>NaN</literal> for
<literal>NaN</literal> inputs to <function>power()</literal>
on older platforms (Dang Minh Huong)
--
Bruce Momjian <br...@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
