Re: [PERFORM] Attempt at work around of int4 query won't touch int8 index ...

2003-09-16 Thread Paul Thomas
On 15/09/2003 08:42 Shridhar Daithankar wrote: Is it possible to follow data type upgrade model in planner? Something like in C/C++ where data types are promoted upwards to find out better plan? int2-int4-int8-float4-float8 types. That could be a clean solution.. just a thought..

Re: [PERFORM] Attempt at work around of int4 query won't touch int8 index ...

2003-09-16 Thread Tom Lane
Paul Thomas [EMAIL PROTECTED] writes: On 15/09/2003 08:42 Shridhar Daithankar wrote: Is it possible to follow data type upgrade model in planner? We have one, more or less. It's not explicitly coded, it emerges from the fact that certain casts are implicit and others are not. For instance,

Re: [PERFORM] Attempt at work around of int4 query won't touch int8 index ...

2003-09-15 Thread Shridhar Daithankar
On 10 Sep 2003 at 22:44, Tom Lane wrote: James Robinson [EMAIL PROTECTED] 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

[PERFORM] Attempt at work around of int4 query won't touch int8 index ...

2003-09-10 Thread James Robinson
Hello, I'm trying a work-around on the index on int8 column gets ignored by planner when queried by literal numbers lacking the explicit '::int8' issue, and had hoped that perhaps I could create a functional index on the result of casting the pk field to int4, and mabye with a little

Re: [PERFORM] Attempt at work around of int4 query won't touch int8 index ...

2003-09-10 Thread Tom Lane
James Robinson [EMAIL PROTECTED] 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