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

From: Andrei Lepikhov <lepihov(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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 14:49:40
Message-ID: ee51b44b-8759-4600-a3af-c0565c9bea12@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 21/3/2025 14:00, Tom Lane wrote:
> Andrei Lepikhov <lepihov(at)gmail(dot)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

Attachment Content-Type Size
scrollable-fix.diff text/plain 2.1 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Richard Guo 2025-03-21 15:09:26 Re: BUG #18859: ERROR: unexpected plan node type: 356
Previous Message Tom Lane 2025-03-21 13:00:53 Re: BUG #18859: ERROR: unexpected plan node type: 356