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

From Robert Haas
Subject Re: Automatic optimization of IN clauses via INNER JOIN
Date
Msg-id 603c8f070912180723s14f374eew466928def9fa6a54@mail.gmail.com
Whole thread Raw
In response to Re: Automatic optimization of IN clauses via INNER JOIN  (Grzegorz Jaśkiewicz <gryzman@gmail.com>)
Responses Re: Automatic optimization of IN clauses via INNER JOIN
List pgsql-performance
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.

...Robert

pgsql-performance by date:

Previous
From: Robert Haas
Date:
Subject: Re: Issues with \copy from file
Next
From: Grzegorz Jaśkiewicz
Date:
Subject: Re: Automatic optimization of IN clauses via INNER JOIN