Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: marian(dot)muller(at)serli(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org, Richard Guo <guofenglinux(at)gmail(dot)com>
Subject: Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list
Date: 2025-12-12 16:54:44
Message-ID: 1018067.1765558484@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> After upgrading to Postgres 18 I've come across an error I wasn't getting
> beforehand. Here's a minimal way to reproduce the issue, that used to work
> well in Postgres 12 and 17 at least.

Thank you for this well-crafted bug report! Bisecting shows that
it broke at

f5050f795aea67dfc40bbc429c8934e9439e22e7 is the first bad commit
commit f5050f795aea67dfc40bbc429c8934e9439e22e7 (HEAD)
Author: Richard Guo <rguo(at)postgresql(dot)org>
Date: Tue Sep 10 12:36:48 2024 +0900

Mark expressions nullable by grouping sets

I have not dug any deeper than that.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message yanliang lei 2025-12-13 04:15:53 Re:Re: Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem.
Previous Message Tom Lane 2025-12-12 15:39:55 Re: BUG #19352: SQL Error messages do not include schema name along with table or data object name.