Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1vU6Pr-00H4Hp-0I
	for pgsql-bugs@arkaria.postgresql.org;
	Fri, 12 Dec 2025 16:54:51 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.96)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1vU6Pp-008msj-0K
	for pgsql-bugs@arkaria.postgresql.org;
	Fri, 12 Dec 2025 16:54:49 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1vU6Po-008msb-2i
	for pgsql-bugs@lists.postgresql.org;
	Fri, 12 Dec 2025 16:54:49 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by magus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1vU6Pn-000Nuv-0F
	for pgsql-bugs@lists.postgresql.org;
	Fri, 12 Dec 2025 16:54:49 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 5BCGsiRB1018068;
	Fri, 12 Dec 2025 11:54:44 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: marian.muller@serli.com
cc: pgsql-bugs@lists.postgresql.org, Richard Guo <guofenglinux@gmail.com>
Subject: Re: BUG #19353: Error XX000 if referencing expanded array in grouping
 set: variable not found in subplan target list
In-reply-to: <19353-aaa179bba986a19b@postgresql.org>
References: <19353-aaa179bba986a19b@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Fri, 12 Dec 2025 10:11:15 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1018066.1765558484.1@sss.pgh.pa.us>
Date: Fri, 12 Dec 2025 11:54:44 -0500
Message-ID: <1018067.1765558484@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/1018067.1765558484%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.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@postgresql.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