Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 77ADF476269 for ; Fri, 15 Mar 2002 16:00:08 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g2FL01S01594; Fri, 15 Mar 2002 16:00:01 -0500 (EST) To: "Gregory Wood" Cc: "Jean-Luc Lachance" , "PostgreSQL-General" Subject: Re: Why is it not using an index? In-reply-to: <003101c1cc60$d98a70e0$7889ffcc@comstock.com> References: <3C924680.4090806@openratings.com> <002801c1cc4f$25dba980$7889ffcc@comstock.com> <3C9258CB.B22E190A@nsd.ca> <003101c1cc60$d98a70e0$7889ffcc@comstock.com> Comments: In-reply-to "Gregory Wood" message dated "Fri, 15 Mar 2002 15:34:46 -0500" Date: Fri, 15 Mar 2002 16:00:00 -0500 Message-ID: <1591.1016226000@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200203/845 X-Sequence-Number: 22217 "Gregory Wood" writes: > It should be. I think the response you'll get from the people on this list > is that they're happy to accept a patch... It's not as easy as you might think to come up with a general-purpose solution --- bearing in mind that Postgres is supposed to support an extensible set of datatypes, and so we'd prefer not to hard-wire much knowledge of specific datatypes into the parser. If you look back a year or two in the pghackers archives, you'll find previous discussions and failed solution proposals. It's still on the TODO list, and eventually someone will come up with a usable answer. regards, tom lane