Re: WIP: patch to create explicit support for semi and anti joins

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <pgsql-hackers(at)postgreSQL(dot)org>,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: WIP: patch to create explicit support for semi and anti joins
Date: 2008-08-21 19:32:28
Message-ID: 48AD7C7C.EE98.0025.0@wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Introduce JOIN_SEMI and JOIN_ANTI join types, the former replacing
> JOIN_IN. Unify the InClauseInfo and OuterJoinInfo infrastructure
into
> "SpecialJoinInfo". Convert IN, EXISTS, and NOT EXISTS clauses at
top
> level of WHERE into semi and anti joins respectively.

It just struck me that this may cause additional joins to count
against the join_collapse_limit. If so, that could cause some
borderline queries to optimize poorly if the limit isn't raised. Is
that a reasonable concern? Possibly something to document in the
release notes?

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message D'Arcy J.M. Cain 2008-08-21 19:54:35 Re: Proposal: new border setting in psql
Previous Message Tom Lane 2008-08-21 19:04:33 Re: [FINALLY] the TODO list has migrated to Wiki