Performance difference between IN(...) and ANY(...) operator

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.


-- 
Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance

[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux