| From: | Anthony Best <abest(at)digitalflex(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Anomaly with SUM(). |
| Date: | 2003-08-08 20:15:18 |
| Message-ID: | 3F3404D6.2020100@digitalflex.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane wrote:
>Anthony Best <abest(at)digitalflex(dot)net> writes:
>
>
>>I've noticed that the SUM() seems to overflow under some situations.
>>The only difference is the order that the data is retrived from the
>>database.
>>
>>
>
>
>
>>accounting=# select sum(amount) from transactions, chart WHERE
>>account=chart.id;
>> sum
>>---------------------
>>5.6843418860808e-14
>>(1 row)
>>
>>
>
>
>
>>accounting=# select sum(amount) from transactions, chart WHERE
>>account=chart.id AND amount=amount;
>>sum
>>-----
>> 0
>>(1 row)
>>
>>
>
>That's not an overflow, it's merely roundoff error. If this surprises
>you, possibly you should be using type NUMERIC instead of float.
>
> regards, tom lane
>
>
Oh, thats right. 'overflow' was the wrong word. I was thinking numeric
was used internally for 'double precision' for some reason.
thank you.
Anthony.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-08-08 20:15:25 | Re: 7.3.3 behaving differently on OS X 10.2.6 and FreeBSD 4.8-STABLE |
| Previous Message | Tom Lane | 2003-08-08 20:08:50 | Re: Trying to create a GiST index in 7.3 |