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 1iRdtb-0005jG-3U for pgsql-bugs@arkaria.postgresql.org; Mon, 04 Nov 2019 15:03:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iRdtZ-0006q2-KA for pgsql-bugs@arkaria.postgresql.org; Mon, 04 Nov 2019 15:03:53 +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 1iRdtZ-0006pu-97 for pgsql-bugs@lists.postgresql.org; Mon, 04 Nov 2019 15:03:53 +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 1iRdtS-00009L-5d for pgsql-bugs@lists.postgresql.org; Mon, 04 Nov 2019 15:03:52 +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 xA4F3jNc006650; Mon, 4 Nov 2019 10:03:45 -0500 From: Tom Lane To: mircea@reva.tech cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16094: Database entering recovery mode In-reply-to: <16094-8fb7061e5370fb00@postgresql.org> References: <16094-8fb7061e5370fb00@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Mon, 04 Nov 2019 14:50:45 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <6648.1572879825.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 04 Nov 2019 10:03:45 -0500 Message-ID: <6649.1572879825@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form writes: > We've updated our database from 10.6 to 12.0 recently and we keep > encountering an error which says that the database is entering recovery > mode. > ... > In the logs the only error we see, is a segmentation fault, when replica= tion > tries to run. It should be possible to collect a stack trace for the segfault, which would greatly assist debugging this. Please see https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_= backend regards, tom lane