From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrei Lepikhov <lepihov@gmail.com>
cc: splarv@ya.ru, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18859: ERROR: unexpected plan node type: 356
In-reply-to: <ee51b44b-8759-4600-a3af-c0565c9bea12@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>
Comments: In-reply-to Andrei Lepikhov <lepihov@gmail.com>
	message dated "Fri, 21 Mar 2025 15:49:40 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1563710.1742571303.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 21 Mar 2025 11:35:03 -0400
Message-ID: <1563711.1742571303@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1563711.1742571303%40sss.pgh.pa.us>
Precedence: bulk

Andrei Lepikhov <lepihov@gmail.com> writes:
> On 21/3/2025 14:00, Tom Lane wrote:
>> Yeah, I'd just come to the same conclusion.  I guess we can make
>> this code look through a Material node as well as Gather.

> Yes, as I see there are no additional corner cases. See the code in =

> attachment.

I think actually we want to use the same processing as for Gather,
in particular the check for a Const.  That's all about what
setrefs.c will do to the plan tree, and it'll do the same things
to Material as it would to Gather.  Since that stanza doesn't
actually do anything that's specific to Gather, the code change
can be as simple as

@@ -8323,7 +8325,7 @@ exec_save_simple_expr(PLpgSQL_expr *expr, CachedPlan=
 *cplan)
 				   ((Result *) plan)->resconstantqual =3D=3D NULL);
 			break;
 		}
-		else if (IsA(plan, Gather))
+		else if (IsA(plan, Gather) || IsA(plan, Material))
 		{
 			Assert(plan->lefttree !=3D NULL &&
 				   plan->righttree =3D=3D NULL &&

I fixed that, did some cosmetic fooling with the comment
and test case, and pushed it.  Thanks for the report,
and for the patch!

			regards, tom lane