From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | rudolphfroger(at)dreamsolution(dot)nl, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Rounding strategy |
Date: | 2021-04-22 17:50:20 |
Message-ID: | 1100756.1619113820@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> On Mon, 2021-04-19 at 08:00 +0000, PG Doc comments form wrote:
>> The 'round' mathematical function documentation doesn't specify its rounding
>> strategy. If this would be documented then users can rely on its rounding
>> behavior. For double precision the rounding probably depends on your
>> platform. For numeric the function seems to round to nearest with ties going
>> away from zero (sometimes referred to as "round half up). 6.5 -> 7.0 and
>> -6.5 -> -7.0.
> Here is a proposed patch.
LGTM, although I think we can be a bit more specific about the float
case. I suggest
... by rounding away from 0. For <type>double precision</type>,
the tie-breaking behavior is platform dependent, but
<quote>round to nearest even</quote> is the most common rule.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2021-04-22 23:51:23 | Re: INCLUDING COMPRESSION (sort enum fields) |
Previous Message | Laurenz Albe | 2021-04-22 16:54:54 | Re: Rounding strategy |