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 1lhDSr-00015J-PB for pgsql-bugs@arkaria.postgresql.org; Thu, 13 May 2021 15:41:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lhDSq-000594-LA for pgsql-bugs@arkaria.postgresql.org; Thu, 13 May 2021 15:41:28 +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 1lhDSq-00058r-Eb for pgsql-bugs@lists.postgresql.org; Thu, 13 May 2021 15:41:28 +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 1lhDSo-0001Aa-6H for pgsql-bugs@lists.postgresql.org; Thu, 13 May 2021 15:41:27 +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 14DFfODl1518255; Thu, 13 May 2021 11:41:24 -0400 From: Tom Lane To: "David G. Johnston" cc: "kamalvarun2004@gmail.com" , "pgsql-bugs@lists.postgresql.org" Subject: Re: BUG #17007: server process (PID XXXX) was terminated by signal 11: Segmentation fault In-reply-to: References: <17007-7b2eddada8ea1bd6@postgresql.org> Comments: In-reply-to "David G. Johnston" message dated "Thu, 13 May 2021 07:41:03 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1518253.1620920484.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Thu, 13 May 2021 11:41:24 -0400 Message-ID: <1518254.1620920484@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "David G. Johnston" writes: > On Thursday, May 13, 2021, PG Bug reporting form > wrote: >> PostgreSQL version: 12.2 >> We are facing an issue once in 2 days that Postgres instance crashes wi= th >> following error > You need to upgrade to a supported version (12.7 in your major version > line). Yeah, that would certainly be the first thing to try. If the problem is still there, we'd really need quite a bit more information to diagnose it. A stack trace from the point of the crash would be quite helpful: https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_= backend Even better would be if you can reduce the problem to a self-contained test case, though I realize that might be hard. regards, tom lane