From: | Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PERFORM] Diferent execution plan for similar query |
Date: | 2003-04-28 11:00:55 |
Message-ID: | 200304281630.55041.shridhar_daithankar@nospam.persistent.co.in |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
On Monday 28 April 2003 16:29, Magnus Naeslund(w) wrote:
> 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.
I would say dig into hackers archives for the consensus(??) reached.. I don't
remember..
Shridhar
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2003-04-28 11:18:55 | Re: INSERT/UPDATE ... RETURNING |
Previous Message | Magnus Naeslund(w) | 2003-04-28 10:59:07 | Re: Diferent execution plan for similar query |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2003-04-28 11:12:06 | Re: Diferent execution plan for similar query |
Previous Message | Magnus Naeslund(w) | 2003-04-28 11:00:03 | Re: Diferent execution plan for similar query |