Re: Multiple-index optimization not working for = ANY operator

"Jimmy Choi" <JCHOI@altera.com> writes:
> I find that it doesn't work (i.e. index is not used and a sequential
> scan is needed), if I have the following instead:
>   SELECT * FROM foo WHERE id = ANY (ARRAY[1,2]);
> Is this expected?

Yes. That construct isn't indexable, period, in any existing release
(it does work in CVS tip though...)

            regards, tom lane