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 1phz68-0003q0-AO for pgsql-general@arkaria.postgresql.org; Thu, 30 Mar 2023 20:42:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1phz67-0008Lt-3S for pgsql-general@arkaria.postgresql.org; Thu, 30 Mar 2023 20:42:15 +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 1phz66-0008Lj-PI for pgsql-general@lists.postgresql.org; Thu, 30 Mar 2023 20:42:14 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1phz63-0005OL-Sz for pgsql-general@lists.postgresql.org; Thu, 30 Mar 2023 20:42:14 +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 32UKgATV286099; Thu, 30 Mar 2023 16:42:10 -0400 From: Tom Lane To: =?utf-8?Q?R=C3=A9beli-Szab=C3=B3_Tam=C3=A1s?= cc: pgsql-general@lists.postgresql.org Subject: Re: recovery long after startup In-reply-to: <598d4a75-57d9-b41a-a927-7584be6278b2@rblst.info> References: <598d4a75-57d9-b41a-a927-7584be6278b2@rblst.info> Comments: In-reply-to =?utf-8?Q?R=C3=A9beli-Szab=C3=B3_Tam=C3=A1s?= message dated "Thu, 30 Mar 2023 20:35:04 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <286097.1680208930.1@sss.pgh.pa.us> Date: Thu, 30 Mar 2023 16:42:10 -0400 Message-ID: <286098.1680208930@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk =?utf-8?Q?R=C3=A9beli-Szab=C3=B3_Tam=C3=A1s?= writes: > I have noticed that a PostgreSQL 13 server went into recovery mode for 2 > seconds during normal operation, not at startup, preventing users from > connecting. The most obvious explanation is that a backend (or other postmaster child process) crashed. I lack an explanation of why your log trace doesn't show anything about that, but that seems like an idea to pursue. What is the logging mechanism you're using? regards, tom lane