Received: from localhost (IDENT:root@hectic-1.jpl.nasa.gov [128.149.68.203]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA83853 for ; Wed, 14 Jul 1999 13:30:26 -0400 (EDT) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1]) by localhost (8.8.7/8.8.7) with ESMTP id RAA30606; Wed, 14 Jul 1999 17:28:52 GMT Sender: lockhart@hub.org Message-ID: <378CC8D3.A9CDD470@alumni.caltech.edu> Date: Wed, 14 Jul 1999 17:28:51 +0000 From: Thomas Lockhart X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686) X-Accept-Language: en MIME-Version: 1.0 To: Tom Lane CC: Constantin Teodorescu , Bruce Momjian , Hannu Krosing , "pgsql-hackers@postgreSQL.org" Subject: Re: [HACKERS] Interesting behaviour ! References: <26012.931970368@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > This might be a relatively simple bug to fix after all, > but it needs more time to find exactly where things are going wrong... > and I have to get some Real Work done... Don't let me stop anyone from looking at this, but fyi this is the one area I didn't yet touch for the "transparent type coersion" work I did for v6.4 and which is still ongoing of course. istm that wherever index use is evaluated one could allow pre-evaluated functions on constants, rather than just strict constants as is the case now. There is a precedent for pre-evaluation of elements of the query tree. If function calls are allowed, then we can try coercing constants using these existing coersion functions, at least when the target column is a "superset type" of the constant. You still run into trouble for cases like select intcol from table1 where intcol < 2.5; - Thomas -- Thomas Lockhart lockhart@alumni.caltech.edu South Pasadena, California