[PERFORM] will the planner ever use an index when the condition is ?

2011-12-17 Thread Roxanne Reid-Bennett
I have a query that used against an indexed column. In this case I can use the reverse and use in or = and get the performance I need... but in general... will the planner ever use an index when the related column is compared using ? I feel like the answer is no, but wanted to ask. Roxanne

Re: [PERFORM] will the planner ever use an index when the condition is ?

2011-12-17 Thread Filip RembiaƂkowski
Normally there is no chance it could work, because (a) the planner does not know all possible values of a column, and (b) btree indexes cannot search on not equal operator. BTW I've just made a case where - logically - it could work, but it still does not: create table nums ( num int4 not null,