Re: not in(subselect) in 8.4 - Mailing list pgsql-performance

From Grzegorz Jaśkiewicz
Subject Re: not in(subselect) in 8.4
Date
Msg-id 2f4958ff0902210910h3c87f0deo5b9d70fac138b1ae@mail.gmail.com
Whole thread Raw
In response to Re: not in(subselect) in 8.4  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: not in(subselect) in 8.4  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
the foo bar example above, with notion that all columns are NOT NULL
behaves much different now. I noticed, that some of the 'anti join'
stuff has changed in cvs recently, but I don't know if that's to
blame.
Basically, what I can see, is that the subselect case is no longer of
lower cost, to the left join - but is quite substantially more
expensive.

Just an observation, I don't intend to use subselects anyhow, because
these are very much slower on 8.3, which we use in production here.

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: not in(subselect) in 8.4
Next
From: Tom Lane
Date:
Subject: Re: not in(subselect) in 8.4