pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Paquier <michael@paquier.xyz>
To: David Rowley <dgrowleyml@gmail.com>
Cc: Jay <liuqi7850@126.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18108: server process was terminated by signal 11: Segmentation fault
Date: Sun, 17 Sep 2023 10:58:56 +0900
Message-ID: <ZQZdYORte8zq0ntI@paquier.xyz> (raw)
In-Reply-To: <CAApHDvrHRYVO9eiK2n7F43DdBvfeSWoayZQSERnqBObh20t_NA@mail.gmail.com>
References: <CAApHDvrDBOkTma2DrXDPctGfLB03xwH2Az9OfrmAf=dLvuvNeg@mail.gmail.com>
	<B2B8335B-A06D-431F-B0E2-6BCC66D306DC@126.com>
	<CAApHDvrHRYVO9eiK2n7F43DdBvfeSWoayZQSERnqBObh20t_NA@mail.gmail.com>

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

Attachments:

  signature.asc (application/pgp-signature, 832B) download

view thread (5+ messages)

Message-ID: <ZQZdYORte8zq0ntI@paquier.xyz>
Permalink:  ../ZQZdYORte8zq0ntI@paquier.xyz/
Also on:    postgresql.org/message-id/ZQZdYORte8zq0ntI@paquier.xyz

 · 

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: pgsql-bugs@postgresql.org
  Cc: michael@paquier.xyz, dgrowleyml@gmail.com, liuqi7850@126.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #18108: server process was terminated by signal 11: Segmentation fault
  In-Reply-To: <ZQZdYORte8zq0ntI@paquier.xyz>

* 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