public inbox for [email protected]  

help / color / mirror / Atom feed
From: =?gb18030?B?t8nT4w==?= <[email protected]>
To: =?gb18030?B?SGF5YXRvIEt1cm9kYSAoRnVqaXRzdSk=?= <[email protected]>
Cc: =?gb18030?B?cGdzcWwtYnVnc0BsaXN0cy5wb3N0Z3Jlc3FsLm9yZw==?= <[email protected]>
Subject: =?gb18030?B?u9i4tKO6UkU6ILvYuLSjulJFOiBCVUcgIzE5NDY0?= =?gb18030?B?OiBTZXJ2ZXIgY3Jhc2ggKFNJR0FCUlQpIHdpdGgg?= =?gb18030?B?VVBEQVRFIGNvbnRhaW5pbmcgbXVsdGlwbGUgICAg?= =?gb18030?B?bXVsdGktY29sdW1uIGFzc2lnbm1lbnRz?=
Date: Tue, 21 Apr 2026 21:11:22 +0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <OS9PR01MB121496039000233ECAFCCF9EAF52C2@OS9PR01MB12149.jpnprd01.prod.outlook.com>
References: <[email protected]>
	<OS9PR01MB121492EEFA805264C8308E9C1F52C2@OS9PR01MB12149.jpnprd01.prod.outlook.com>
	<[email protected]>
	<OS9PR01MB121496039000233ECAFCCF9EAF52C2@OS9PR01MB12149.jpnprd01.prod.outlook.com>

Hi Developer,&nbsp;
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




------------------&nbsp;原始邮件&nbsp;------------------
发件人:                                                                                                                        "Hayato Kuroda (Fujitsu)"                                                                                    <[email protected]&gt;;
发送时间:&nbsp;2026年4月21日(星期二) 晚上9:00
收件人:&nbsp;"飞鱼"<[email protected]&gt;;
抄送:&nbsp;"[email protected]"<[email protected]&gt;;
主题:&nbsp;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

reply
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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: =?gb18030?B?u9i4tKO6UkU6ILvYuLSjulJFOiBCVUcgIzE5NDY0?= =?gb18030?B?OiBTZXJ2ZXIgY3Jhc2ggKFNJR0FCUlQpIHdpdGgg?= =?gb18030?B?VVBEQVRFIGNvbnRhaW5pbmcgbXVsdGlwbGUgICAg?= =?gb18030?B?bXVsdGktY29sdW1uIGFzc2lnbm1lbnRz?=
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox