Skip site navigation (1) Skip section navigation (2)

Re: Pls Hlp: SQL Problem

From: "Fernando Hevia" <fhevia(at)ip-tel(dot)com(dot)ar>
To: "'Scott Marlowe'" <scott(dot)marlowe(at)gmail(dot)com>
Cc: "'Hengky Lie'" <hengkyliwandouw(at)gmail(dot)com>,"'pgsql-sql'" <pgsql-sql(at)postgresql(dot)org>
Subject: Re: Pls Hlp: SQL Problem
Date: 2008-09-15 20:14:25
Message-ID: 019001c9176f$a5ff7200$ (view raw, whole thread or download thread mbox)
Lists: pgsql-sql

> -----Mensaje original-----
> De: Scott Marlowe [mailto:scott(dot)marlowe(at)gmail(dot)com] 

> >
> > Consider that if you are NOT going to use the decimals you should 
> > really use integer or bigint datatypes. The numeric type 
> compute much 
> > slower than integer datatypes.
> Note that if you're just converting the output the cost is 
> minimal compared to if you're doing all your math in numeric. 
>  It's when you force math to happen that numeric is slower, 
> but numeric's gotten a lot of tuning in the last few years 
> and it's withing a few percentage
> of integer for most measurements.   Definitely not twice as slow or
> anything like they once were.

Well, in that case the manual should be revised.

8.1.2. Arbitrary Precision Numbers

The type numeric can store numbers with up to 1000 digits of precision and
perform calculations exactly. It is especially recommended for storing
monetary amounts and other quantities where exactness is required. However,
arithmetic on numeric values is __very slow__ compared to the integer types,
or to the floating-point types described in the next section. 


The explicit "very slow" assertion scared me quite enough so to avoid
numeric types where possible.


In response to


pgsql-sql by date

Next:From: Scott MarloweDate: 2008-09-15 20:18:31
Subject: Re: Pls Hlp: SQL Problem
Previous:From: Andreas KretschmerDate: 2008-09-15 12:01:26
Subject: Re: select from two tables

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group