Re: NOT IN subquery optimization

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Li, Zheng" <zhelli(at)amazon(dot)com>
Cc: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, "Finnerty, Jim" <jfinnert(at)amazon(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: NOT IN subquery optimization
Date: 2019-02-27 00:13:54
Message-ID: 17354.1551226434@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Li, Zheng" <zhelli(at)amazon(dot)com> writes:
> However, given that the March CommitFest is imminent and the runtime smarts patent concerns David had pointed out (which I was not aware of before), we would not move that direction at the moment.

> I propose that we collaborate to build one patch from the two patches submitted in this thread for the CF.

TBH, I think it's very unlikely that any patch for this will be seriously
considered for commit in v12. It would be against project policy, and
spending a lot of time reviewing the patch would be quite unfair to other
patches that have been in the queue longer. Therefore, I'd suggest that
you not bend things out of shape just to have some patch to submit before
March 1. It'd be better to work with the goal of having a coherent patch
ready for the first v13 CF, probably July-ish.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-02-27 00:21:40 Re: Autovaccuum vs temp tables crash
Previous Message Andres Freund 2019-02-27 00:10:55 Re: Pluggable Storage - Andres's take