Re: BUG #18859: ERROR: unexpected plan node type: 356

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Richard Guo <guofenglinux(at)gmail(dot)com>
Cc: Andrei Lepikhov <lepihov(at)gmail(dot)com>, splarv(at)ya(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18859: ERROR: unexpected plan node type: 356
Date: 2025-03-21 15:36:14
Message-ID: 1563855.1742571374@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Richard Guo <guofenglinux(at)gmail(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2025-03-24 15:28:31 BUG #18862: using pg_autoctl node_2 cannot bring back from maintenance mode
Previous Message Tom Lane 2025-03-21 15:35:03 Re: BUG #18859: ERROR: unexpected plan node type: 356