Re: Attempt at work around of int4 query won't touch int8 index ... - Mailing list pgsql-performance

From Tom Lane
Subject Re: Attempt at work around of int4 query won't touch int8 index ...
Date
Msg-id 20901.1063248257@sss.pgh.pa.us
Whole thread Raw
In response to Attempt at work around of int4 query won't touch int8 index ...  (James Robinson <jlrobins@socialserve.com>)
Responses Re: Attempt at work around of int4 query won't touch int8 index ...  ("Shridhar Daithankar" <shridhar_daithankar@persistent.co.in>)
List pgsql-performance
James Robinson <jlrobins@socialserve.com> 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

pgsql-performance by date:

Previous
From: James Robinson
Date:
Subject: Attempt at work around of int4 query won't touch int8 index ...
Next
From: Josh Berkus
Date:
Subject: Re: Reading data in bulk - help?