Re: Automatic optimization of IN clauses via INNER JOIN - Mailing list pgsql-performance

From Grzegorz Jaśkiewicz
Subject Re: Automatic optimization of IN clauses via INNER JOIN
Date
Msg-id 2f4958ff0912180724t58940a36q1770df3609b38f1d@mail.gmail.com
Whole thread Raw
In response to Re: Automatic optimization of IN clauses via INNER JOIN  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Automatic optimization of IN clauses via INNER JOIN  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-performance
2009/12/18 Robert Haas <robertmhaas@gmail.com>:
> 2009/12/18 Grzegorz Jaśkiewicz <gryzman@gmail.com>:
>> On Fri, Dec 18, 2009 at 2:18 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>>
>>> NOT IN is the only that really kills you as far as optimization is
>>> concerned.  IN can be transformed to a join.  NOT IN forces a NOT
>>> (subplan)-type plan, which bites - hard.
>>
>> in a well designed database (read: not abusing NULLs) - it can be done
>> with joins too.
>
> But not by PostgreSQL, or so I believe.

using left join ?



--
GJ

pgsql-performance by date:

Previous
From: Robert Haas
Date:
Subject: Re: Automatic optimization of IN clauses via INNER JOIN
Next
From: "Michael N. Mikhulya"
Date:
Subject: Idea how to get rid of Bitmap Heap Scan