A. Kretschmer wrote:
> in a SELECT with a condition 'WHERE foo IN (1,2,3,4,...)' with a large
...
> But if the list increase the planner choose an seq-scan. The amount of
> values in the list is about 200 and the table has about 250.000 rows.
>
> How can we avoid the seq-scan?
Are you sure you'd want to? What plan have you found to be faster with
200 tests?
--
Richard Huxton
Archonet Ltd