Hi Developer,
Thanks for the quick reply. I have also verified the other three bugs on PG 15.17, and none of them are reproducible either. These issues appear to be specific to the build environment based on merge commit 7103ebb7aa and update commit 86dc9005, which is the exact version I used for commit-level testing. They seem to be tied to the transient state of the code at that particular commit—subsequent releases likely fixed or refactored the relevant code paths.
Best regards,
Chunling
------------------ 原始邮件 ------------------
发件人: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>;
发送时间: 2026年4月21日(星期二) 晚上9:00
收件人: "飞鱼"<303677365@qq.com>;
抄送: "pgsql-bugs@lists.postgresql.org"<pgsql-bugs@lists.postgresql.org>;
主题: RE: 回复：RE: BUG #19464: Server crash (SIGABRT) with UPDATE containing multiple multi-column assignments
Dear 飞鱼,
Thanks for the quick confirmation. I suggest you to confirm the same for other reports [1], [2] and [3].
[1]: https://www.postgresql.org/message-id/19461-8d03395b71f86664%40postgresql.org
[2]: https://www.postgresql.org/message-id/19462-563c85bec169995a%40postgresql.org
[3]: https://www.postgresql.org/message-id/19463-f59d5d2a41969756%40postgresql.org
Best regards,
Hayato Kuroda
FUJITSU LIMITED
