Обсуждение: Performance difference between IN(...) and ANY(...) operator

Hi,

I'm using both IN and ANY() operators extensively my application.  Can
anybody answer me on the following questions:
    1) Which operator is advantage over the another, interms of performance?
    2) If I've indexed these columns, will both the operators make use of index
scanning?
    3) Also I read from PostgreSQL documentation that there is a limit in
passing values to IN operator.  As far as I remember, it is 1000, but then I
don't have the web  link justifying this handy now.  If yes/no, is it
applicable for ANY operator also?
    4) Is there any difference in framing queries at query planner level?

Regards,
Gnanam
--
View this message in context:
http://www.nabble.com/Performance-difference-between-IN%28...%29-and-ANY%28...%29-operator-tp24386330p24386330.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.

On Wed, Jul 8, 2009 at 2:50 AM, Gnanam<gnanam@zoniac.com> wrote:
> I'm using both IN and ANY() operators extensively my application.  Can
> anybody answer me on the following questions:
>        1) Which operator is advantage over the another, interms of performance?
>        2) If I've indexed these columns, will both the operators make use of index
> scanning?
>        3) Also I read from PostgreSQL documentation that there is a limit in
> passing values to IN operator.  As far as I remember, it is 1000, but then I
> don't have the web  link justifying this handy now.  If yes/no, is it
> applicable for ANY operator also?
>        4) Is there any difference in framing queries at query planner level?

You might want to have a look at this email, and Tom Lane's reply:

http://archives.postgresql.org/message-id/603c8f070810251131m4e9cf4efl8c6e877d1fbd2022@mail.gmail.com

...Robert