Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iUuEv-0000u2-4N for pgsql-bugs@arkaria.postgresql.org; Wed, 13 Nov 2019 15:07:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iUuEs-0004Zc-P6 for pgsql-bugs@arkaria.postgresql.org; Wed, 13 Nov 2019 15:07:22 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iUuEs-0004ZF-Di for pgsql-bugs@lists.postgresql.org; Wed, 13 Nov 2019 15:07:22 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iUuEf-0000LO-TH for pgsql-bugs@lists.postgresql.org; Wed, 13 Nov 2019 15:07:15 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id xADF73dr006162; Wed, 13 Nov 2019 10:07:04 -0500 From: Tom Lane To: kjonca@fastmail.com (Kamil =?iso-8859-2?Q?Jo=F1ca?=) cc: Michael Paquier , pgsql-bugs@lists.postgresql.org Subject: Re: Random crashes - segmentation fault In-reply-to: <87tv77digm.fsf@alfa.kjonca> References: <871rucdwkt.fsf@alfa.kjonca> <20191113125832.GZ1549@paquier.xyz> <87tv77digm.fsf@alfa.kjonca> Comments: In-reply-to kjonca@fastmail.com (Kamil =?iso-8859-2?Q?Jo=F1ca?=) message dated "Wed, 13 Nov 2019 14:16:57 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <6160.1573657623.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 13 Nov 2019 10:07:03 -0500 Message-ID: <6161.1573657623@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk kjonca@fastmail.com (Kamil =3D?iso-8859-2?Q?Jo=3DF1ca?=3D) writes: > Michael Paquier writes: >> Could it be possible to see a backtrace of the crash? There is > Erm. Only thing I can do is to configure for debug future crashes. Could= you > tell me what and how to configure to get backtrace? There's some accumulated wisdom at https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_= backend I'd suggest that before worrying about that, you should install 12.1 (official release is tomorrow) and see if the crashes go away. There's not much info in this report, but it could match any of several already-fixed bugs. regards, tom lane