Re: Wrong results from an antijoin

From: wenhui qiu <qiuwenhuifx(at)gmail(dot)com>
To: Richard Guo <guofenglinux(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Wrong results from an antijoin
Date: 2026-10-13 02:09:36
Message-ID: CAGjGUA+G7J1GFs9zRhVeL4s8EwTiH_WVKSeF5m7GYocidC=kVw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

HI Richard

> > Makes sense. But the query you suggested doesn't not work.
> > int4_tbl.f1 and tenk1.unique1 are both nullable, so the NOT IN is not
> > converted to an antijoin. In v2 I added a NOT IN test that works.
> > (That test won't be in the back-patches for v16 to v18.)
> Thank you for pointing out the mistake. the v2 path LGTM

Thanks

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Chee Wooson 2026-10-13 01:47:54 Re: Re: [PATCH] Discard aborted updaters when expanding a multixact