Re: Memoize ANTI and SEMI JOIN inner - Mailing list pgsql-hackers

From Richard Guo
Subject Re: Memoize ANTI and SEMI JOIN inner
Date
Msg-id CAMbWs49F9oR30P3AfQor_i-xLBEVuUOJvTxvzpy_wf-11PUYCw@mail.gmail.com
Whole thread Raw
In response to Re: Memoize ANTI and SEMI JOIN inner  (Andrei Lepikhov <lepihov@gmail.com>)
Responses Re: Memoize ANTI and SEMI JOIN inner
List pgsql-hackers
On Mon, Mar 31, 2025 at 7:33 PM Andrei Lepikhov <lepihov@gmail.com> wrote:
> and I don't get the case. As I see, ANTI/SEMI join just transforms to
> the regular join and it is still not the case. May you be more specific?

Upthread, you said that a qual contained in ppi_clauses will also be
included in extra->restrictlist.  I provided this example to show that
this is not true.  And it seems to me that this discrepancy makes the
check I mentioned earlier not reliable in all cases.  As I explained
earlier, this check could pass even if a restriction clause isn't
parameterized, as long as another join clause, which doesn't belong to
the current join, is included in ppi_clauses.  This is not correct.

This isn't about your patch, but about the master code.  However, if
this code is incorrect, your patch will also behave incorrectly, since
you patch relies on and extends this check.

Thanks
Richard



pgsql-hackers by date:

Previous
From: Richard Guo
Date:
Subject: Re: Reduce "Var IS [NOT] NULL" quals during constant folding
Next
From: Ashutosh Bapat
Date:
Subject: statistics import and export: another difference in dump/restore