On 01/27/2011 08:18 AM, Tom Lane wrote:
Not if you can persuade the client-side code to output integers as integers. "numeric" type is orders of magnitude slower than integers.
I sadly have to vouch for this. My company converted an old Oracle app and they changed all their primary keys (and foreign keys, and random larger int fields) to NUMERIC(19)'s. I've convinced them all new stuff should be BIGINT if they need that level of coverage, but the damage is already done.
I'm not sure about orders of magnitude on the storage/index side, but my tests gave us a 10% boost if just the keys are switched over to INT or BIGINT.
-- Shaun Thomas OptionsHouse | 141 W. Jackson Blvd. | Suite 800 | Chicago IL, 60604 312-676-8870 stho...@peak6.com ______________________________________________ See http://www.peak6.com/email_disclaimer.php for terms and conditions related to this email -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
