Performance implications of numeric?

From: Wells Oliver <wellsoliver(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Performance implications of numeric?
Date: 2012-08-22 04:27:10
Message-ID: CAOC+FBWN3AMo5LbH-8WSMvP1bixNUTLXJ+4X4ehDcShfRK=HzQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

We have a lot of tables which store numeric data. These tables all use the
numeric type, where the values are 95% integer values. We used numeric
because it eliminated the need for casting during division to yield a
floating point value.

I'm curious as to whether this would have performance and/or disk size
implications. Would converting these columns to integer (or double
precision on the handful that require the precision) and forcing developers
to use explicit casting be worth the time?

Thanks for any clarification.

--
Wells Oliver
wellsoliver(at)gmail(dot)com

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Craig Ringer 2012-08-22 04:33:15 Re: Grant problem and how to prevent users to execute OS commands?
Previous Message Scott Marlowe 2012-08-22 04:19:01 Re: Problems with timestamp with time zone and old dates?