From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrei Lepikhov <lepihov@gmail.com>
Cc: splarv@ya.ru
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18859: ERROR: unexpected plan node type: 356
Date: Fri, 21 Mar 2025 09:00:53 -0400
Message-ID: <1243263.1742562053@sss.pgh.pa.us> (raw)
In-Reply-To: <72c3c1f4-9ed1-4d1c-ae67-eb04b8e50cd1@gmail.com>
References: <18859-0d5f28ac99a37059@postgresql.org>
<72c3c1f4-9ed1-4d1c-ae67-eb04b8e50cd1@gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, lepihov@gmail.com, splarv@ya.ru, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18859: ERROR: unexpected plan node type: 356
In-Reply-To: <1243263.1742562053@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox