Re: NOT IN subquery optimization

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Richard Guo <riguo(at)pivotal(dot)io>, "Li, Zheng" <zhelli(at)amazon(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-03-01 22:57:58
Message-ID: 1674.1551481078@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> writes:
> On Sat, 2 Mar 2019 at 05:44, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I'm not sure if the second one is actually a semantics bug or just a
>> misoptimization? But yeah, +1 for putting in some simple tests for
>> corner cases right now. Anyone want to propose a specific patch?

> The second is just reducing the planner's flexibility to produce a
> good plan. The first is a bug. Proposed regression test attached.

LGTM, pushed.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Li, Zheng 2019-03-01 22:58:42 Re: NOT IN subquery optimization
Previous Message Tom Lane 2019-03-01 22:34:13 Re: Infinity vs Error for division by zero