Re: Planner : anti-join on left joins

From: Tender Wang <tndrwang(at)gmail(dot)com>
To: Richard Guo <guofenglinux(at)gmail(dot)com>
Cc: Nicolas Adenis-Lamarre <nicolas(dot)adenis(dot)lamarre(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Planner : anti-join on left joins
Date: 2026-02-13 02:17:55
Message-ID: CAHewXNnwrrAPtAJjiNHnhnkcdN+ZfsJHDV0aMxbkgCZxnerM=Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Richard Guo <guofenglinux(at)gmail(dot)com> 于2026年2月12日周四 14:43写道:
>
> On Tue, Jan 6, 2026 at 5:23 PM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
> > The logic 'strict for b.z' effectively applies only if b.z happens to
> > be the join key b.y. To avoid confusion, I have rephrased the comment
> > to make this distinction clear.
> >
> > I've also included a commit message, refined the comments throughout,
> > and added test cases in the updated patch.
> >
> > Feedback and testing are very welcome.
>
> I've pushed this patch.
>
> - Richard

Thanks for making this optimization workable and pushing.

--
Thanks,
Tender Wang

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zhijie Hou (Fujitsu) 2026-02-13 02:24:50 RE: Improve pg_sync_replication_slots() to wait for primary to advance
Previous Message Hayato Kuroda (Fujitsu) 2026-02-13 02:03:01 RE: BUG: Former primary node might stuck when started as a standby