| From: | Anthony Best <abest(at)digitalflex(dot)net> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Anomaly with SUM(). |
| Date: | 2003-08-08 20:01:15 |
| Message-ID: | 3F34018B.2080403@digitalflex.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Stephan Szabo wrote:
>On Fri, 8 Aug 2003, Anthony Best wrote:
>
>
>
>>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.
>>
>>
>
>Is amount a float type column (float4 or float8)? If so, you're probably
>just running into issues with float precision problems. Changing the
>order of the operations can change the final value of a sequence of
>operations on float.
>
>
It's "double precision." (Which is float8?).
So, should I tweak my join to preserve order, or something else?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-08-08 20:08:50 | Re: Trying to create a GiST index in 7.3 |
| Previous Message | Tom Lane | 2003-08-08 19:50:55 | Re: Anomaly with SUM(). |