David Greco <David_Greco@xxxxxxxxxxxxxxx> 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 -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
