| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | rschaaf(at)commoninf(dot)com, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #12885: The result of casting a double to an integer depends on the database version |
| Date: | 2015-03-24 03:12:00 |
| Message-ID: | 26862.1427166720@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
> On Tue, Mar 24, 2015 at 11:27 AM, Michael Paquier wrote:
>> On a Windows 7 box with code compiled with MSVC 2010 I am seeing the
>> same behavior as Rich. This looks like a bug in ~9.3 that meritates
>> some attention assuming that the latter behavior is legit.
> And MinGW outputs the latter, similarly to other platforms... I'll investigate.
Look for something about setting the IEEE float rounding mode. "Round to
nearest even" is standard in most places, but it would not astonish me
to hear that Microsoft got that wrong.
If it is wrong I don't know that we'd want to back-patch a behavioral
change, but I'd definitely vote for conforming to the norm in 9.5
and later.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-03-24 06:25:57 | Re: BUG #12885: The result of casting a double to an integer depends on the database version |
| Previous Message | Michael Paquier | 2015-03-24 02:42:16 | Re: BUG #12885: The result of casting a double to an integer depends on the database version |