X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 98C9AD1B4E3 for ; Thu, 11 Sep 2003 02:44:29 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 21425-09 for ; Wed, 10 Sep 2003 23:44:23 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 3A85AD1B4E2 for ; Wed, 10 Sep 2003 23:44:17 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h8B2iIAn020902; Wed, 10 Sep 2003 22:44:19 -0400 (EDT) To: James Robinson Cc: pgsql-performance@postgresql.org Subject: Re: Attempt at work around of int4 query won't touch int8 index ... In-reply-to: <2756862E-E3F5-11D7-8513-000A9566A412@socialserve.com> References: <2756862E-E3F5-11D7-8513-000A9566A412@socialserve.com> Comments: In-reply-to James Robinson message dated "Wed, 10 Sep 2003 21:13:29 -0400" Date: Wed, 10 Sep 2003 22:44:17 -0400 Message-ID: <20901.1063248257@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/183 X-Sequence-Number: 3549 James Robinson writes: > Is this just a dead end, or is there some variation of this that might > possibly work, so that ultimately an undoctored literal number, when > applied to an int8 column, could find an index? I think it's a dead end. What I was playing with this afternoon was removing the int8-and-int4 comparison operators from pg_operator. It works as far as making "int8col = 42" do the right thing, but I'm not sure yet about side-effects. regards, tom lane