Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 786292E031E for ; Wed, 12 Dec 2007 21:03:23 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 22168-09 for ; Wed, 12 Dec 2007 21:03:13 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 10FA02E02DC for ; Wed, 12 Dec 2007 21:03:17 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id lBD13FM4029423; Wed, 12 Dec 2007 20:03:15 -0500 (EST) To: Richard Broersma Jr cc: Medi Montaseri , pgsql-admin@postgresql.org Subject: Re: WHERE clause OR vs IN In-reply-to: <359993.87392.qm@web31808.mail.mud.yahoo.com> References: <359993.87392.qm@web31808.mail.mud.yahoo.com> Comments: In-reply-to Richard Broersma Jr message dated "Wed, 12 Dec 2007 16:37:45 -0800" Date: Wed, 12 Dec 2007 20:03:15 -0500 Message-ID: <29422.1197507795@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/75 X-Sequence-Number: 27592 Richard Broersma Jr writes: > --- On Wed, 12/12/07, Medi Montaseri wrote: >> based on your report, run time of OR is 0.275 ms and IN is >> 0.314 >> > postgres=# explain analyze select * from tellers where >> bid in ('1','2'); > Two other options are: > SELECT * > FROM Tellers > WHERE bin = ANY( '1', '2' ); Note that depending on which PG version you are testing, x IN (a,b,c) is exactly equivalent to x=a OR x=b OR x=c (older versions), or to x = ANY(ARRAYa,b,c]) (newer versions). > SELECT T.* > FROM Tellers AS T > INNER JOIN ( VALUES ( '1' ), ( '2' ) ) AS B( bin ) > ON T.bin = B.bin; I seriously doubt that one's gonna win ... regards, tom lane