Re: Wrong results from an antijoin

From: Dongpo Liu <poe(dot)liu(at)pm(dot)me>
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-28 20:26:02
Message-ID: R5FtRWiCaK1Y5arvs56i0kWY-m2X3_MrFWcepu9jSlV4-EaWM6IJ0gXXjtEbBz1N1jSFUyF-jYSdQXMWJ7VjVpj-L5lDfEQlqv0jh6awuc0=@pm.me
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Richard,

> I left convert_ANY_sublink_to_join alone in this patch, since the fix
> needs to go back to v16 and that change isn't needed for it. We can
> do it as a follow-up cleanup on master.

Attached is the follow-up cleanup for master. It builds the subquery RTE
directly in convert_ANY_sublink_to_join(), without a dummy ParseState.

The patch builds and passes the core regression tests.

Regards,
Dongpo Liu

Attachment Content-Type Size
v1-0001-Build-subquery-RTEs-directly-for-ANY-sublinks.patch application/octet-stream 2.8 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Manu 2026-10-28 20:27:56 Re: O(N^3) planning time in choose_plan_name() since 8c49a484e8e
Previous Message Salma Elsayed 2026-10-28 20:17:37 Re: PoC: Simplify recovery after dropping a table by LOGGING the restore LSN