Skip site navigation (1) Skip section navigation (2)

Re: Real vs Int performance

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Greco <David_Greco(at)harte-hanks(dot)com>
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Real vs Int performance
Date: 2011-01-27 14:18:11
Message-ID: 21353.1296137891@sss.pgh.pa.us (view raw, whole thread or download thread mbox)
Thread:
Lists: pgsql-performance
David Greco <David_Greco(at)harte-hanks(dot)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

In response to

Responses

pgsql-performance by date

Next:From: Shaun ThomasDate: 2011-01-27 14:30:15
Subject: Re: Real vs Int performance
Previous:From: Shaun ThomasDate: 2011-01-27 14:17:23
Subject: Re: Why I lost the last pg_xlog file?

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group