From: | Shaun Thomas <sthomas(at)optionshouse(dot)com> |
---|---|
To: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>, testman1316 <danilo(dot)ramirez(at)hmhco(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PostrgeSQL vs oracle doing 1 million sqrts am I doing it wrong? |
Date: | 2014-08-05 14:44:19 |
Message-ID: | 53E0EDC3.4050200@optionshouse.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 08/05/2014 12:56 AM, Mark Kirkwood wrote:
> The moral of the story for this case is that mapping Oracle to Postgres
> datatypes can require some careful thought. Using 'native' types (like
> integer, float8 etc) will generally give vastly quicker performance.
We've seen a lot of this ourselves. Oracle's NUMERIC is a native type,
whereas ours is emulated. From the performance, it would appear that
REAL is another calculated type.
At least you used INT though. I've seen too many Oracle shops using
NUMERIC in PostgreSQL because it's there, and suffering major
performance hits because of it.
That said, the documentation here says FLOAT4 is an alias for REAL, so
it's somewhat nonintuitive for FLOAT4 to be so much slower than FLOAT8,
which is an alias for DOUBLE PRECISION.
http://www.postgresql.org/docs/9.3/static/datatype.html
Not sure why that would be.
--
Shaun Thomas
OptionsHouse, LLC | 141 W. Jackson Blvd. | Suite 800 | Chicago IL, 60604
312-676-8870
sthomas(at)optionshouse(dot)com
______________________________________________
See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2014-08-05 15:51:51 | Re: Scaling shared buffer eviction |
Previous Message | Fujii Masao | 2014-08-05 14:34:07 | Re: Audit of logout |