Re: Diferent execution plan for similar query

From: "Magnus Naeslund(w)" <mag(at)fbab(dot)net>
To: "Shridhar Daithankar" <shridhar_daithankar(at)persistent(dot)co(dot)in>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Diferent execution plan for similar query
Date: 2003-04-28 10:59:07
Message-ID: 59937.129.178.88.66.1051527547.squirrel@mail2.fbab.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance


Shridhar Daithankar said:
>
> In second case, postgresql typecasted it correctly. Even
> eans.id_iean=345::int8 would have worked the same way. By default
> postgresql
> treats a number as int4 while comparing and integer and float8 for a real
> numbe. I discovered that yesterday.
>
> Until the planner/parser gets smarter, this is going to be an FAQ..
>
> Shridhar

Is this an nontrivial change?
Because if it's trivial it should be done, imho.
I've been bitten indirectly of this, and it's not too easy to find out
always. I think that this is one of the most unobvious performance hickups
there are with postgresql.

Magnus

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Shridhar Daithankar 2003-04-28 11:00:55 Re: [PERFORM] Diferent execution plan for similar query
Previous Message Shridhar Daithankar 2003-04-28 10:41:33 Re: Diferent execution plan for similar query

Browse pgsql-performance by date

  From Date Subject
Next Message Magnus Naeslund(w) 2003-04-28 11:00:03 Re: Diferent execution plan for similar query
Previous Message Shridhar Daithankar 2003-04-28 10:41:33 Re: Diferent execution plan for similar query