Horton
Menu

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

PG Bug reporting form <noreply@postgresql.org>

View thread
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: splarv@ya.ru
Date: 2025-03-20T13:53:59Z
Lists: pgsql-bugs 
The following bug has been logged on the website:

Bug reference:      18859
Logged by:          Olleg Samoylov
Email address:      splarv@ya.ru
PostgreSQL version: 17.4
Operating system:   RedOS 8
Description:        

This working.
postgres=> do $$ declare p_CurData refcursor; begin OPEN p_CurData FOR
SELECT NULL::int id; end;$$;
DO
But this is not. Internal error.
postgres=> do $$ declare p_CurData refcursor; begin OPEN p_CurData SCROLL
FOR SELECT NULL::int id; end;$$;
ERROR:  unexpected plan node type: 356
CONTEXT:  PL/pgSQL function inline_code_block line 1 at OPEN

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.