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

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrei Lepikhov <lepihov@gmail.com>
Cc: splarv@ya.ru, pgsql-bugs@lists.postgresql.org
Date: 2025-03-21T13:00:53Z
Lists: pgsql-bugs
Andrei Lepikhov <lepihov@gmail.com> writes:
> The problem here is in the scrollable cursors code which inserts 
> Material node:

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.

			regards, tom lane



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Fix plpgsql's handling of simple expressions in scrollable cursors.