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 ) id 1makLW-00055f-H0 for pgsql-bugs@arkaria.postgresql.org; Wed, 13 Oct 2021 19:55:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1makLV-0008Hb-Dd for pgsql-bugs@arkaria.postgresql.org; Wed, 13 Oct 2021 19:55:25 +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 ) id 1makLV-0008HR-6M for pgsql-bugs@lists.postgresql.org; Wed, 13 Oct 2021 19:55:25 +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 ) id 1makLS-0003ak-VX for pgsql-bugs@lists.postgresql.org; Wed, 13 Oct 2021 19:55:24 +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 19DJtMHi666113; Wed, 13 Oct 2021 15:55:22 -0400 From: Tom Lane To: ejberdecia@yahoo.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17229: Segmentation Fault after upgrading to version 13 In-reply-to: <17229-bc836b4d1d2633bf@postgresql.org> References: <17229-bc836b4d1d2633bf@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Wed, 13 Oct 2021 17:57:05 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <666111.1634154922.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 13 Oct 2021 15:55:22 -0400 Message-ID: <666112.1634154922@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form writes: > Ever since we upgraded to PostgreSQL version 13 we are sporadically gett= ing > segmentation faults for the following process and all existing connectio= ns > get killed and our streaming replication process goes down. Hmm, can you get a stack trace from the crash? See https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_= backend regards, tom lane