Horton
Menu

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

Andrei Lepikhov <lepihov@gmail.com>

View thread
From: Andrei Lepikhov <lepihov@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: splarv@ya.ru, pgsql-bugs@lists.postgresql.org
Date: 2025-03-21T14:49:40Z
Lists: pgsql-bugs

Attachments

On 21/3/2025 14:00, Tom Lane wrote:
> 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.
Yes, as I see there are no additional corner cases. See the code in 
attachment.

-- 
regards, Andrei Lepikhov

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.