Re: Diferent execution plan for similar query - Mailing list pgsql-performance

From Magnus Naeslund(w)
Subject Re: Diferent execution plan for similar query
Date
Msg-id 62257.129.178.88.66.1051527603.squirrel@mail2.fbab.net
Whole thread Raw
In response to Diferent execution plan for similar query  (<jgimenez@sipec_quitaesto_.es>)
Responses Re: Diferent execution plan for similar query  (Andrew Sullivan <andrew@libertyrms.info>)
List 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


pgsql-performance by date:

Previous
From: "Magnus Naeslund(w)"
Date:
Subject: Re: Diferent execution plan for similar query
Next
From: Shridhar Daithankar
Date:
Subject: Re: Diferent execution plan for similar query