Re: BUG #18859: ERROR: unexpected plan node type: 356
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Richard Guo <guofenglinux@gmail.com>
Cc: Andrei Lepikhov <lepihov@gmail.com>, splarv@ya.ru,
pgsql-bugs@lists.postgresql.org
Date: 2025-03-21T15:36:14Z
Lists: pgsql-bugs
Richard Guo <guofenglinux@gmail.com> writes: > 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. Right, I'd come to the same conclusion before seeing your message. regards, tom lane
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix plpgsql's handling of simple expressions in scrollable cursors.
- c196c610b339 14.18 landed
- a28c1fb619bf 16.9 landed
- 7fe312f6092f 18.0 landed
- 5e56efa7c0e0 15.13 landed
- 1353b1161a79 17.5 landed
- 0f60e1fba137 13.21 landed