Re: Postgres 11 release notes - Mailing list pgsql-hackers

From David Rowley
Subject Re: Postgres 11 release notes
Date
Msg-id CAKJS1f_xVHwGkR0iL=AsFbJERm6-di=B3z4YW1DZMs4WgfQwyQ@mail.gmail.com
Whole thread Raw
In response to Re: Postgres 11 release notes  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses NaNs in numeric_power (was Re: Postgres 11 release notes)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 16 May 2018 at 02:01, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> David Rowley <david.rowley@2ndquadrant.com> writes:
>> While I'm not in favour of removing Dang's credit here, technically
>> this patch was Tom's. The code added in float.c by Dang's patch
>> (61b200e2f) was effectively reverted by 6bdf1303.  Dang's regression
>> tests remain, so should also be credited along with Tom.
>
> I'm not particularly fussed about getting credit for that.  However,
> looking again at how that patch series turned out --- ie, that
> we ensured POSIX behavior for NaNs only in HEAD --- I wonder
> whether we shouldn't do what was mentioned in the commit log for
> 6bdf1303, and teach numeric_pow() about these same special cases.
> It seems like it would be more consistent to change both functions
> for v11, rather than letting that other shoe drop in some future
> major release.

I'm inclined to agree. It's hard to imagine these two functions
behaving differently in regards to NaN input is useful to anyone.

-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Pantelis Theodosiou
Date:
Subject: Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11
Next
From: Bruce Momjian
Date:
Subject: Re: Postgres 11 release notes