Re: Performance of IN (...) vs. = ANY array[...] - Mailing list pgsql-performance

From Tom Lane
Subject Re: Performance of IN (...) vs. = ANY array[...]
Date
Msg-id 5373.1158351561@sss.pgh.pa.us
Whole thread Raw
In response to Performance of IN (...) vs. = ANY array[...]  (Benjamin Minshall <minshall@intellicon.biz>)
List pgsql-performance
Benjamin Minshall <minshall@intellicon.biz> writes:
> What are the advantages or disadvantages of using arrays in this
> situation?  The = ANY array method makes plpgsql development cleaner,
> but seems to really lack performance in certain cases.

In existing releases, the form with IN (list-of-scalar-constants)
can be optimized into indexscan(s), but = ANY (array) isn't.

8.2 will treat them equivalently (in fact, it converts IN (...) to
= ANY (ARRAY[...]) !).  So depending on your time horizon, you might
wish to stick with whichever is cleaner for your calling code.

            regards, tom lane

pgsql-performance by date:

Previous
From: Benjamin Minshall
Date:
Subject: Performance of IN (...) vs. = ANY array[...]
Next
From: "Luke Lonergan"
Date:
Subject: Re: RAID 0 not as fast as expected