Add a heuristic to transformAExprIn() to make it prefer expanding "x IN (list)"
into an OR of equality comparisons, rather than x = ANY(ARRAY[...]), when there
are Vars in the right-hand side. This avoids a performance regression compared
to pre-8.2 releases, in cases where the OR form can be optimized into scans
of multiple indexes. Limit the possible downside by preferring this form only
when the list isn't very long (I set the cutoff at 32 elements, which is a
bit arbitrary but in the right ballpark). Per discussion with Jim Nasby.
In passing, also make it try the OR form if it cannot select a common type
for the array elements; we've seen a complaint or two about how the OR form
worked for such cases and ARRAY doesn't.
parse_coerce.c (r2.146 -> r22.214.171.124)
parse_expr.c (r1.198 -> r126.96.36.199)
pgsql-committers by date
|Next:||From: Tom Lane||Date: 2008-10-25 19:51:32|
|Subject: pgsql: Be a little smarter about qual handling for semi-joins: a qual |
|Previous:||From: Tom Lane||Date: 2008-10-25 17:19:17|
|Subject: pgsql: Add a heuristic to transformAExprIn() to make it prefer expanding |