Re: Float/Double cast to int - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Float/Double cast to int
Date
Msg-id CAB7nPqQzP+phGo4A7bcEkcpY4C_tbFK-fBfk3Vapgy=boYoi3g@mail.gmail.com
Whole thread Raw
In response to Re: Float/Double cast to int  (Feng Tian <ftian@vitessedata.com>)
List pgsql-hackers
On Fri, May 22, 2015 at 4:33 AM, Feng Tian <ftian@vitessedata.com> wrote:
> Ah, thanks!  I did not realize numeric comes into play.   But, this is even
> more interesting -- I would expect numeric is more consistent than
> float/double when dealing with stuff like rounding.
>
> I missed the not too long ago discussion, :-)   Regardless of the mechanisms
> underneath, it would be quite hard to explain this behavior to customer.
> Maybe it is time to be brave, and be compatible with reality instead of
> backward?

Here is some food for thought:
- The original thread of pgsql-bug where this has been discussed first

http://www.postgresql.org/message-id/flat/20150320194337.2573.72944@wrigleys.postgresql.org#20150320194337.2573.72944@wrigleys.postgresql.org
- Another thread to document this behavior more appropriately (patch pending)
http://www.postgresql.org/message-id/CAB7nPqRVCbvYAWL++vCfyzOUujEay21bcLbBk_Mb=+2JX7+e5A@mail.gmail.com
Regards,
--
Michael



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: jsonb concatenate operator's semantics seem questionable
Next
From: Peter Geoghegan
Date:
Subject: Re: INSERT ... ON CONFLICT DO UPDATE with _any_ constraint