From: | David Teran <david(dot)teran(at)cluster9(dot)com> |
---|---|
To: | Shridhar Daithankar <shridhar_daithankar(at)myrealbox(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: optimizing Postgres queries |
Date: | 2004-01-05 12:18:06 |
Message-ID: | 3796212E-3F79-11D8-A528-000A95A6F0DC@cluster9.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi,
> The performance will likely to be the same. Its just that integer
> happens to
> be default integer type and hence it does not need an explicit
> typecast. ( I
> don't remember exactly which integer is default but it is either of
> int2,int4
> and int8...:-))
>
The docs say int4 is much faster than int8, but i will check this.
> The performance diffference is likely due to use of index, which is in
> turn
> due to typecasting. If you need bigint, you should use them. Just
> remember to
> typecast whenever required.
This is my bigger problem: i am using EOF (OR mapping tool) which frees
me more or less form writing a lot of SQL. If i need to typecast to use
an index then i have to see how to do this with this framework.
Regards David
From | Date | Subject | |
---|---|---|---|
Next Message | Shridhar Daithankar | 2004-01-05 12:37:53 | Re: optimizing Postgres queries |
Previous Message | Shridhar Daithankar | 2004-01-05 12:10:05 | Re: optimizing Postgres queries |