Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xRn86-00000001Jtv-1ICu for pgsql-bugs@arkaria.postgresql.org; Fri, 13 Nov 2026 08:59:30 +0000 Received: from localhost ([127.0.0.1]:42542 helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xRn84-00000009QYa-3dAq for pgsql-bugs@arkaria.postgresql.org; Fri, 13 Nov 2026 08:59:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]:33170) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xRWQH-000000020ps-0HJ1 for pgsql-bugs@lists.postgresql.org; Thu, 12 Nov 2026 15:09:09 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xRWQE-00000000gfy-1V5J for pgsql-bugs@lists.postgresql.org; Thu, 12 Nov 2026 15:09:08 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=khk1QEnc594f4fGoa2Xdek3dDbTICEu6r7PeQA/5c2c=; b=mKWlzo0oFrXvEDOj0rozzO5rHZ dsn/WxEu9jXt0gw66se7DP6tHV/Hvriru8YSmVzsr8NS5JBKYJ/aB5eLBr5rqK/8s2gGjgnhdIlxP PIVh2De1HswLmT8t+Bt0yH8yzoaDmkiPzxNjm0A8fVJyvT8yKky6dLupprWzIuFkCdQ9L05p4fP3G tpU6Q2OiUgXWmurnKaFo2tR/lwHZpmlNDnuZRBx02Kkq6kOj3AblVv/gr+6L7ylgApqvz+bveog7N Ef3HMaw5LuCZo7795LBNbZnaBx/Ha3C8d3IopNwmbbGSP7s2D6gtoVSWgD0qVUCJJVyjDK4ON4yY9 WhPCuPZA==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xRWQC-00000001Ywd-1tlr for pgsql-bugs@lists.postgresql.org; Thu, 12 Nov 2026 15:09:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xRWQB-00000003xl8-1FAH for pgsql-bugs@lists.postgresql.org; Thu, 12 Nov 2026 15:09:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: BUG #19897: Recovery fails after "LOG: consistent recovery state reached" To: pgsql-bugs@lists.postgresql.org From: PG Bug reporting form Cc: harukat@sraoss.co.jp Reply-To: harukat@sraoss.co.jp, pgsql-bugs@lists.postgresql.org Date: Thu, 12 Nov 2026 15:08:29 +0000 Message-ID: <19897-60cf65e39604f958@postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following bug has been logged on the website: Bug reference: 19897 Logged by: Haruka Takatsuka Email address: harukat@sraoss.co.jp PostgreSQL version: 15.0 Operating system: Linux Description: =20 When using the following procedure to recover a base backup taken from a standby, the service would sometimes fail to start up with log messages in the following strange sequence: LOG: consistent recovery state reached at ... LOG: invalid record length at ... FATAL: recovery ended before configured recovery target was reached LOG: database system is ready to accept read-only connections LOG: startup process (PID 1234) exited with exit code 1 The base backup had the same result after repeated attempts. (recovery steps) $ rm -f data/15.5reco/log/* $ rm data/15.5reco/standby.signal $ touch data/15.5reco/recovery.signal $ cat >> data/15.5reco/postgresql.conf <