Skip site navigation (1) Skip section navigation (2)

Re: [PERFORM] Diferent execution plan for similar query

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 (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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


In response to

pgsql-performance by date

Next:From: Andrew SullivanDate: 2003-04-28 11:12:06
Subject: Re: Diferent execution plan for similar query
Previous:From: Magnus Naeslund(w)Date: 2003-04-28 11:00:03
Subject: Re: Diferent execution plan for similar query

pgsql-hackers by date

Next:From: Jan WieckDate: 2003-04-28 11:18:55
Subject: Re: INSERT/UPDATE ... RETURNING
Previous:From: Magnus Naeslund(w)Date: 2003-04-28 10:59:07
Subject: Re: Diferent execution plan for similar query

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group