Re: BUG #19883: Partition pruning errors on SubPlan inside = ANY array

From: Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com>
To: imchifan(at)163(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19883: Partition pruning errors on SubPlan inside = ANY array
Date: 2026-11-12 20:19:19
Message-ID: CAB8bMiuhnNoxAB2QzT=naYJyrgtRX3BUUrEnR5Q-YSYPxQ9bHw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

чт, 12 нояб. 2026 г. в 22:16, PG Bug reporting form <noreply(at)postgresql(dot)org
>:

>
> On PostgreSQL 18.6 on Linux/amd64, a SELECT against a range-partitioned
> table fails with `ERROR: SubPlan found with no parent plan` when an `= ANY`
> array element contains an uncorrelated SubPlan whose expression evaluates
> to
> NULL.
>
>
Hi Liu,
Fix in master eacee6b6187 (Richard Guo, backpatched to 18). In REL_18_7,
fixed by 70ffc30e12b.
We need to upgrade to 18.7 if possible.

--
Regards,
Rachitskiy Andrey

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Corey Huinker 2026-11-12 21:07:54 Re: BUG #19842: pg_restore_extended_stats() rejects a faithful pg_dump of ANALYZE-produced range expression statisti
Previous Message Tom Lane 2026-11-12 19:56:13 Re: BUG #19848: BEGIN ATOMIC with unnamed/OUT params breaks restore and pg_upgrade