Performance implications of numeric? - Mailing list pgsql-general

From Wells Oliver
Subject Performance implications of numeric?
Date
Msg-id CAOC+FBWN3AMo5LbH-8WSMvP1bixNUTLXJ+4X4ehDcShfRK=HzQ@mail.gmail.com
Whole thread Raw
Responses Re: Performance implications of numeric?  (Craig Ringer <ringerc@ringerc.id.au>)
Re: Performance implications of numeric?  (Merlin Moncure <mmoncure@gmail.com>)
List 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@gmail.com

pgsql-general by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: Problems with timestamp with time zone and old dates?
Next
From: Craig Ringer
Date:
Subject: Re: Grant problem and how to prevent users to execute OS commands?