On Fri, Sep 15, 2023 at 10:19:41PM +1200, David Rowley wrote:
> On Fri, 15 Sept 2023 at 22:11, Jay <liuqi7850@126.com> wrote:
>>
>> I reproduced the operation and got this stack trace:
>>
>> Program received signal SIGSEGV, Segmentation fault.
>>
>> 0x00007efe187b4598 in __memcpy_ssse3_back () from /lib64/libc.so.6
>>
>> Continuing.
>
> Please send the output of: bt full
A few more things.
The bug report refers to 15.2. Please note that there have been a few
fixes in the area of MERGE in 15.3, while the latest minor version of
15.X released is 15.4. So could you update to 15.4 and check if your
problem happens again when running this version?
Another thing that would save a lot of time for all of us would be to
provide a self-contained test case, with a minimal schema for the test
case involved, as there could be things related to the table's schema
itself that could influence the issue, say indexes, foreign keys, etc.
If you send such a test case, you'd better make sure that any
sensitive data is obfuscated.
--
Michael
