On Fri, Dec 18, 2009 at 2:18 PM, Robert Haas <robertmhaas@xxxxxxxxx> 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. -- GJ -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
