Re: NOT IN subquery optimization

From: Richard Guo <riguo(at)pivotal(dot)io>
To: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
Cc: Jim Finnerty <jfinnert(at)amazon(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: NOT IN subquery optimization
Date: 2019-02-27 06:14:16
Message-ID: CAN_9JTyrC4Gr9EU-8kif74jcGazE3qhu4nciwpTC_F_=i7fVUA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 27, 2019 at 4:52 AM David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
wrote:

> On Wed, 27 Feb 2019 at 03:07, Jim Finnerty <jfinnert(at)amazon(dot)com> wrote:
>
> If you're proposing to do that for this thread then I can take my
> planner only patch somewhere else. I only posted my patch as I pretty
> much already had what I thought you were originally talking about.
> However, please be aware there are current patents around adding
> execution time smarts in this area, so it's probably unlikely you'll
> find a way to do this in the executor that does not infringe on those.
> Probably no committer would want to touch it. I think my patch covers
> a good number of use cases and as far as I understand, does not go
> near any current patents.
>
> Thanks for pointing out the patent concerns. I was not aware of that
before.
Could you please provide some clue where I can find more info about the
patents?

Thanks
Richard

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2019-02-27 06:15:44 Re: When is the MessageContext released?
Previous Message Andy Fan 2019-02-27 06:08:47 When is the MessageContext released?