X-Original-To: pgsql-hackers@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 35265475E14 for ; Mon, 28 Apr 2003 07:01:16 -0400 (EDT) Received: from www.pspl.co.in (www.pspl.co.in [202.54.11.65]) by postgresql.org (Postfix) with ESMTP id 1B960475B99 for ; Mon, 28 Apr 2003 07:01:14 -0400 (EDT) Received: (from root@localhost) by www.pspl.co.in (8.11.6/8.11.6) id h3SB1Fm12275 for ; Mon, 28 Apr 2003 16:31:15 +0530 Received: from daithan.intranet.pspl.co.in (daithan.intranet.pspl.co.in [192.168.7.161]) by www.pspl.co.in (8.11.6/8.11.0) with ESMTP id h3SB1Fx12265; Mon, 28 Apr 2003 16:31:15 +0530 From: Shridhar Daithankar To: pgsql-performance@postgresql.org Subject: Re: [PERFORM] Diferent execution plan for similar query Date: Mon, 28 Apr 2003 16:30:55 +0530 User-Agent: KMail/1.5.1 References: <003401c30d70$92c07310$8001010a@sipec.es> <200304281611.33669.shridhar_daithankar@nospam.persistent.co.in> <59937.129.178.88.66.1051527547.squirrel@mail2.fbab.net> In-Reply-To: <59937.129.178.88.66.1051527547.squirrel@mail2.fbab.net> Cc: pgsql-hackers@postgresql.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200304281630.55041.shridhar_daithankar@nospam.persistent.co.in> X-Spam-Status: No, hits=-38.9 required=5.0 tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_KMAIL version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) X-Archive-Number: 200304/953 X-Sequence-Number: 38443 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