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

Поиск
Список
Период
Сортировка
От Richard Guo
Тема Re: BUG #18859: ERROR: unexpected plan node type: 356
Дата
Msg-id CAMbWs49RHCfv9Kna0Hd=8dG1Pm8J=0HCCy6tkFjHz-xs024uBw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #18859: ERROR: unexpected plan node type: 356  (Andrei Lepikhov <lepihov@gmail.com>)
Ответы Re: BUG #18859: ERROR: unexpected plan node type: 356
Список pgsql-bugs
On Fri, Mar 21, 2025 at 11:49 PM Andrei Lepikhov <lepihov@gmail.com> wrote:
> 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.

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.

-       else if (IsA(plan, Gather))
+       else if (IsA(plan, Gather) || IsA(plan, Material))

Thanks
Richard



В списке pgsql-bugs по дате отправления: