Re: FW: performance issue with a 2.5gb joinded table - Mailing list pgsql-performance

From Tom Lane
Subject Re: FW: performance issue with a 2.5gb joinded table
Date
Msg-id 24975.1357332051@sss.pgh.pa.us
Whole thread Raw
In response to Re: FW: performance issue with a 2.5gb joinded table  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: FW: performance issue with a 2.5gb joinded table
List pgsql-performance
Heikki Linnakangas <hlinnakangas@vmware.com> writes:
> One difference is that numerics are stored more tightly packed on
> Oracle. Which is particularly good for Oracle as they don't have other
> numeric data types than number. On PostgreSQL, you'll want to use int4
> for ID-fields, where possible. An int4 always takes up 4 bytes, while a
> numeric holding an integer value in the same range is typically 5-9 bytes.

Replacing those numeric(8) and numeric(16) fields with int4 and int8
would be greatly beneficial to comparison and hashing performance,
not just table size.  I'm a bit surprised that EDB's porting tools
evidently don't do this automatically (I infer from the reference to
PPAS that the OP is using EDB ...)

            regards, tom lane


pgsql-performance by date:

Previous
From: Claudio Freire
Date:
Subject: Re: Re[2]: [PERFORM] SMP on a heavy loaded database
Next
From: nobody nowhere
Date:
Subject: Re[4]: [PERFORM] Re[2]: [PERFORM] SMP on a heavy loaded database