Re: SQL command speed

Kate Collins  writes:
> I did some experimentation, and if the WHERE clause had one or two items
> it would use the index; more and it would not.

Kate, it is reasonable behavior for the planner to stop using
indexscans when there are enough OR clauses.  Each OR clause requires
a separate indexscan and so eventually it'll be cheaper to just do one
sequential scan over the whole table.  What we appear to have here is
a case of misestimation of the relative costs of index and sequential
scans, leading the planner to switch too soon.  Next question is why
the misestimation.  It's difficult to say anything without seeing
your EXPLAIN results for different numbers of OR clauses.  Also, how
big is the table (how many rows) and how many rows do you actually
get from the query?
		regards, tom lane