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.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1tvePz-006kzT-6K
	for pgsql-bugs@arkaria.postgresql.org; Fri, 21 Mar 2025 15:36:19 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1tvePx-009rMT-Tp
	for pgsql-bugs@arkaria.postgresql.org; Fri, 21 Mar 2025 15:36:17 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1tvePx-009rML-Lx
	for pgsql-bugs@lists.postgresql.org; Fri, 21 Mar 2025 15:36:17 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by makus.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 1tvePw-000L0o-0F
	for pgsql-bugs@lists.postgresql.org;
	Fri, 21 Mar 2025 15:36:16 +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 52LFaEaA1563856;
	Fri, 21 Mar 2025 11:36:14 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Richard Guo <guofenglinux@gmail.com>
cc: Andrei Lepikhov <lepihov@gmail.com>, splarv@ya.ru,
        pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18859: ERROR: unexpected plan node type: 356
In-reply-to: 
 <CAMbWs49RHCfv9Kna0Hd=8dG1Pm8J=0HCCy6tkFjHz-xs024uBw@mail.gmail.com>
References: <18859-0d5f28ac99a37059@postgresql.org>
 <72c3c1f4-9ed1-4d1c-ae67-eb04b8e50cd1@gmail.com>
 <1243263.1742562053@sss.pgh.pa.us>
 <ee51b44b-8759-4600-a3af-c0565c9bea12@gmail.com>
 <CAMbWs49RHCfv9Kna0Hd=8dG1Pm8J=0HCCy6tkFjHz-xs024uBw@mail.gmail.com>
Comments: In-reply-to Richard Guo <guofenglinux@gmail.com>
	message dated "Sat, 22 Mar 2025 00:09:26 +0900"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1563854.1742571374.1@sss.pgh.pa.us>
Date: Fri, 21 Mar 2025 11:36:14 -0400
Message-ID: <1563855.1742571374@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/1563855.1742571374%40sss.pgh.pa.us>
Precedence: bulk

Richard Guo <guofenglinux@gmail.com> writes:
> A Material's tlist could also be a Const copied up by setrefs.c, in
> which case we can avoid looking further, similar to what Gather does.
> I wonder if we could have Material use the same handle as Gather.

Right, I'd come to the same conclusion before seeing your message.

			regards, tom lane