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.96) (envelope-from ) id 1w0jo9-002ANf-2a for pgsql-bugs@arkaria.postgresql.org; Thu, 12 Mar 2026 17:26:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w0jo8-00GALm-0d for pgsql-bugs@arkaria.postgresql.org; Thu, 12 Mar 2026 17:26:48 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w0ima-00FpuU-0I for pgsql-bugs@lists.postgresql.org; Thu, 12 Mar 2026 16:21:08 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1w0imX-00000001nIR-2WVO for pgsql-bugs@lists.postgresql.org; Thu, 12 Mar 2026 16:21:07 +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=2iUj3U6ft+cculVX56haOsLuQP9uDnR67vkvKeYz/V8=; b=RB/qOrdokRbzFo9zO9DMyEF3lq +cIpnEx+TYSb/JQ/4rhjWOclTlhYx9n4FLJY2snLppx9h0kdhM0p7E80Zwl1k/U3IHnkUlAJj8Ddc gjz6OeVcjFMdLOzO5PFOLAqoPKPFREv8Pm3X7q9niCOXUxthRERepHGksjQLRVov0GQ87Y32nvSnK xTbdNkLQgKq23WoMh9SIZ5ZjZ7pHGAaf+YG1h9kDK39IEZ06xPz39dLvDKwUsTA11YLhnkZJ1/8Ve 14rfW+kG9129u03pfkH/QcSxEc1GA6wBQPHSSkNaNzClAld/lLuaH14+0SK27nbvlxu3Xq7RCqDsR PtjsfK4g==; 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.96) (envelope-from ) id 1w0imW-004T82-23 for pgsql-bugs@lists.postgresql.org; Thu, 12 Mar 2026 16:21:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w0imT-0096u5-2M for pgsql-bugs@lists.postgresql.org; Thu, 12 Mar 2026 16:21:02 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: BUG #19432: recovery fails at invalid checkpoint record To: pgsql-bugs@lists.postgresql.org From: PG Bug reporting form Cc: felix.hamme@ionos.com Reply-To: felix.hamme@ionos.com, pgsql-bugs@lists.postgresql.org Date: Thu, 12 Mar 2026 16:20:30 +0000 Message-ID: <19432-3c569e9472f42cee@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: 19432 Logged by: Felix Hamme Email address: felix.hamme@ionos.com PostgreSQL version: 17.9 Operating system: Debian 13 Description: =20 Hi, I'm trying to restore from a pg_basebackup at timeline 1 to a restore_target_time in timeline 2. It fails at "invalid checkpoint record", "could not locate required checkpoint record at 0/3000080". All relevant wal files are in the archive, the restore_command works and backup_label, pg_controldata, pg_waldump and 00000002.history look like everything should work. Recovering only timeline 1 works, but it fails as soon as it should proceed in timeline 2. A 6.7MB tar of the basebackup and the wal archive is available at https://get.hidrive.com/i/PwMejRQG . This link expires on 2026-03-13, I can provide a new link if needed. Why does this recovery fail?