From: | "Radhika Sambamurti" <radhika(at)88thstreet(dot)com> |
---|---|
To: | "Andrew Sullivan" <ajs(at)crankycanuck(dot)ca> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Floating point type to store numbers |
Date: | 2007-04-17 20:33:33 |
Message-ID: | 19968.63.118.86.10.1176842013.squirrel@www.88thstreet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Andrew,
This has been quite helpful. My main concern is CPU cost. Thanks for the
input.
--Radhika
> On Tue, Apr 17, 2007 at 02:53:54PM -0400, Radhika Sambamurti wrote:
>> that hold money fields and rates from varchar to float. I do not want to
>> convert to numeric because numeric is a special string type.
>
> I think you should reconsider. The _only_ correct storage for your
> money data (i.e. if you want to do calculations on them) is numeric.
> Float is always wrong, in every application, for this sort of work.
> Obviously, you can store the values as text, but if you want to do
> calculations, you'll need to cast (in which case you're casting to
> numeric, I hope, or you could lose precision).
>
>> The question is: how accurate is floating point numbers in Postgres. We
>
> As accurate as they are in the underlying C implementation, which is
> to say "not accurate enough for financial data".
>
> A
>
> --
> Andrew Sullivan | ajs(at)crankycanuck(dot)ca
> A certain description of men are for getting out of debt, yet are
> against all taxes for raising money to pay it off.
> --Alexander Hamilton
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
--
It is all a matter of perspective. You choose your view by choosing where
to stand.
Larry Wall
---
From | Date | Subject | |
---|---|---|---|
Next Message | Radhika Sambamurti | 2007-04-17 20:36:20 | Re: Floating point type to store numbers |
Previous Message | Radhika Sambamurti | 2007-04-17 20:28:04 | Re: Floating point type to store numbers |