From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Greco <David_Greco@harte-hanks.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Real vs Int performance
Date: Thu, 27 Jan 2011 09:18:11 -0500
Message-ID: <21353.1296137891@sss.pgh.pa.us> (raw)
In-Reply-To: <CDFA9340E95A764E9366B4EDF3A43125BCACF7E9EC@VA3DIAXVS091.RED001.local>
References: <CDFA9340E95A764E9366B4EDF3A43125BCACF7E68D@VA3DIAXVS091.RED001.local>
<26917.1296079932@sss.pgh.pa.us>
<CDFA9340E95A764E9366B4EDF3A43125BCACF7E9EC@VA3DIAXVS091.RED001.local>
David Greco <David_Greco@harte-hanks.com> writes:
> Right you are. Kettle is turning the number(11) field from Oracle into
> a BigNumber, which is a decimal. If I cast the field into an Integer
> in Kettle and keep the field an integer in Postgres, I get good
> performance. Suspect the correct course of action would simply be to
> make number(11) fields in Oracle numeric(11,0) fields in Postgres.
Not if you can persuade the client-side code to output integers as
integers. "numeric" type is orders of magnitude slower than integers.
regards, tom lane
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, David_Greco@harte-hanks.com
Subject: Re: Real vs Int performance
In-Reply-To: <21353.1296137891@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