Re: Performance difference between IN(...) and ANY(...) operator - Mailing list pgsql-performance

From Robert Haas
Subject Re: Performance difference between IN(...) and ANY(...) operator
Date
Msg-id 603c8f070907231622r1b98b937r7722258f267c71d@mail.gmail.com
Whole thread Raw
In response to Performance difference between IN(...) and ANY(...) operator  (Gnanam <gnanam@zoniac.com>)
List pgsql-performance
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

pgsql-performance by date:

Previous
From: "Lauris Ulmanis"
Date:
Subject: Postgres user authentification or LDAP authentification
Next
From: "WANGRUNGVICHAISRI, SHIVESH"
Date:
Subject: Configuring Postgresql for writing BLOB at a high-rate