Re: Optimizing NOT IN plans / verify rewrite - Mailing list pgsql-performance

From Maciek Sakrejda
Subject Re: Optimizing NOT IN plans / verify rewrite
Date
Msg-id AANLkTin=-ZKfcZwSdWv03SzMeKGszHq=87k-hwHM3BRq@mail.gmail.com
Whole thread Raw
In response to Re: Optimizing NOT IN plans / verify rewrite  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Optimizing NOT IN plans / verify rewrite  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-performance
> Can "b" be null in any of these tables?  If not, then you can
> rewrite your query to us NOT EXISTS and have the same semantics.
> That will often be much faster.

Thanks, Kevin.

No NULLs. It looks like it's a good deal slower than the LOJ version,
but a good deal faster than the original. Since the equivalence of
semantics is much easier to verify here, we may go with this (at least
for the moment).
---
Maciek Sakrejda | System Architect | Truviso

1065 E. Hillsdale Blvd., Suite 230
Foster City, CA 94404
(650) 242-3500 Main
www.truviso.com

pgsql-performance by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Optimizing NOT IN plans / verify rewrite
Next
From: "Kevin Grittner"
Date:
Subject: Re: Optimizing NOT IN plans / verify rewrite