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 1kuzlp-0006ao-Sf for pgsql-bugs@arkaria.postgresql.org; Thu, 31 Dec 2020 15:21:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kuzlo-0007CK-Gf for pgsql-bugs@arkaria.postgresql.org; Thu, 31 Dec 2020 15:21:44 +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 1kuzlo-0007CC-9O for pgsql-bugs@lists.postgresql.org; Thu, 31 Dec 2020 15:21:44 +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 1kuzlh-0005Fe-Rd for pgsql-bugs@lists.postgresql.org; Thu, 31 Dec 2020 15:21:43 +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 0BVFLZvb2452477; Thu, 31 Dec 2020 10:21:35 -0500 From: Tom Lane To: oleg9301@gmail.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16799: postgresql log issue(last completed transaction was at log time) In-reply-to: <16799-af1b66268fe20d0d@postgresql.org> References: <16799-af1b66268fe20d0d@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Thu, 31 Dec 2020 14:52:58 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2452475.1609428095.1@sss.pgh.pa.us> Date: Thu, 31 Dec 2020 10:21:35 -0500 Message-ID: <2452476.1609428095@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form writes: > After recovering postgresql from barman, in version 12.5 I don't have next > string > "last completed transaction was at log time %s" > In postgresql 11.9-1.pgdg100+1 everything fine. I don't see any reason to believe there's a bug here. That message would only appear if at least one transaction commit or abort record was replayed from WAL, and it's quite possible there wouldn't have been. regards, tom lane