Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1kYbc5-0000g5-Ee
	for pgsql-bugs@arkaria.postgresql.org; Fri, 30 Oct 2020 21:07:09 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1kYbc4-00083U-29
	for pgsql-bugs@arkaria.postgresql.org; Fri, 30 Oct 2020 21:07:08 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1kYbc3-00083L-Rw
	for pgsql-bugs@lists.postgresql.org; Fri, 30 Oct 2020 21:07:07 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1kYbc1-0005h3-Mo
	for pgsql-bugs@lists.postgresql.org; Fri, 30 Oct 2020 21:07:06 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 09UL74ej136657;
	Fri, 30 Oct 2020 17:07:04 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: luis.roberto@siscobra.com.br
cc: pgsql-bugs <pgsql-bugs@lists.postgresql.org>,
        "alan.formagi" <alan.formagi@siscobra.com.br>
Subject: Re: segfault with incremental sort
In-reply-to: 
 <1807748588.37862034.1604091799640.JavaMail.zimbra@siscobra.com.br>
References: <622580997.37108180.1604080457319.JavaMail.zimbra@siscobra.com.br>
 <102089.1604082122@sss.pgh.pa.us>
 <541187747.37582276.1604086719237.JavaMail.zimbra@siscobra.com.br>
 <107029.1604087483@sss.pgh.pa.us>
 <1673261949.37800156.1604090102715.JavaMail.zimbra@siscobra.com.br>
 <1807748588.37862034.1604091799640.JavaMail.zimbra@siscobra.com.br>
Comments: In-reply-to luis.roberto@siscobra.com.br
	message dated "Fri, 30 Oct 2020 18:03:19 -0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <136655.1604092024.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 30 Oct 2020 17:07:04 -0400
Message-ID: <136656.1604092024@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Precedence: bulk

luis.roberto@siscobra.com.br writes:
> I also managed to find a coredump from systemd, if you want,I can send a=
 link... it's 290MB, though. =


Not much use in that, nobody else could do anything without the
matching debug symbols either.

> I can see messages like this, using journalctl -xe: =


> Stack trace of thread 548078: =

> #0 0x0000000000665ee4 ExecSubPlan (/usr/pgsql-13/bin/postgres) =


Hm ... suggestive, but not really enough to debug it.

Can you build a self-contained test case?

			regards, tom lane