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 1jMBQA-0007Rq-CY for pgsql-bugs@arkaria.postgresql.org; Wed, 08 Apr 2020 14:11:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jMBQ9-0003Ar-9I for pgsql-bugs@arkaria.postgresql.org; Wed, 08 Apr 2020 14:11:13 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jMBQ9-00039k-3E for pgsql-bugs@lists.postgresql.org; Wed, 08 Apr 2020 14:11:13 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jMBQ6-0001ce-5u for pgsql-bugs@lists.postgresql.org; Wed, 08 Apr 2020 14:11:12 +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 038EAx55001651; Wed, 8 Apr 2020 10:10:59 -0400 From: Tom Lane To: Hamid Akhtar cc: johannes.mols@googlemail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16351: PostgreSQL closing connection during requests with segmentation fault In-reply-to: References: <16351-5cac06fa29fc19e1@postgresql.org> Comments: In-reply-to Hamid Akhtar message dated "Wed, 08 Apr 2020 17:15:40 +0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1649.1586355059.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 08 Apr 2020 10:10:59 -0400 Message-ID: <1650.1586355059@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hamid Akhtar writes: > Unfortunately, there isn't enough information here for anybody to reprod= uce > the issue. Yeah. There is some info here about extracting a stack trace, which could be quite helpful: https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_= backend regards, tom lane