Re: Query plan change with multiple elements in IN clause - Mailing list pgsql-performance

From Tom Lane
Subject Re: Query plan change with multiple elements in IN clause
Date
Msg-id 5899.1377871228@sss.pgh.pa.us
Whole thread Raw
In response to Query plan change with multiple elements in IN clause  (Mathieu De Zutter <mathieu@dezutter.org>)
List pgsql-performance
Mathieu De Zutter <mathieu@dezutter.org> writes:
> The problem is that this join is performing very badly when more than one
> work is involved. It chooses a plan that is orders of magnitude slower.

> I have attached
> - The (simplified) table definitions
> - The (simplified) view
> - Two queries with explain analyze plan: "IN (1)" => fast, "IN (1,3)" =>
> slow
> - postgresql.conf

The reason you get a nice plan in the first case is that "w.id in (1)"
is treated as "w.id = 1", and then there is logic that combines that with
"w.id = wps.id" to conclude that we can synthesize a condition "wps.id = 1".
None of that happens when there's more than one IN item, because it's not
an equality operator anymore.

You might be able to do something like
    JOIN (VALUES (1),(3)) foo(x) ON w.id = foo.x

            regards, tom lane


pgsql-performance by date:

Previous
From: Mathieu De Zutter
Date:
Subject: Query plan change with multiple elements in IN clause
Next
From: Łukasz Walkowski
Date:
Subject: Varchar vs foreign key vs enumerator - table and index size