2009/12/18 Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>:
> On Fri, Dec 18, 2009 at 2:18 PM, Robert Haas <robertmhaas(at)gmail(dot)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.
In response to
pgsql-performance by date
|Next:||From: Grzegorz Jaśkiewicz||Date: 2009-12-18 15:24:46|
|Subject: Re: Automatic optimization of IN clauses via INNER JOIN|
|Previous:||From: Robert Haas||Date: 2009-12-18 15:23:01|
|Subject: Re: Issues with \copy from file|