From: Tom Lane <tgl@sss.pgh.pa.us>
To: Heikki Linnakangas <hlinnakangas@vmware.com>
Cc: Daniel Westermann <Daniel.Westermann@lcsystems.ch>
Cc: 'pgsql-performance@postgresql.org' <pgsql-performance@postgresql.org>
Subject: Re: FW: performance issue with a 2.5gb joinded table
Date: Fri, 04 Jan 2013 15:40:51 -0500
Message-ID: <24975.1357332051@sss.pgh.pa.us> (raw)
In-Reply-To: <50E5B990.5010101@vmware.com>
References: <05F9B935C9F93D4DA5ED64B6D321477C215B00@bsw00i-1402.lcsys.ch>
<05F9B935C9F93D4DA5ED64B6D321477C215B25@bsw00i-1402.lcsys.ch>
<50E5B990.5010101@vmware.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, hlinnakangas@vmware.com, Daniel.Westermann@lcsystems.ch
Subject: Re: FW: performance issue with a 2.5gb joinded table
In-Reply-To: <24975.1357332051@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox