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 1vrJeh-00ERvj-12 for pgsql-bugs@arkaria.postgresql.org; Sat, 14 Feb 2026 17:42:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vrJee-0002Tv-05 for pgsql-bugs@arkaria.postgresql.org; Sat, 14 Feb 2026 17:42:04 +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 1vrJed-0002Tm-22 for pgsql-bugs@lists.postgresql.org; Sat, 14 Feb 2026 17:42:03 +0000 Received: from forwardcorp1a.mail.yandex.net ([2a02:6b8:c0e:500:1:45:d181:df01]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vrJeZ-00000000cmx-2AYB for pgsql-bugs@lists.postgresql.org; Sat, 14 Feb 2026 17:42:02 +0000 Received: from mail-nwsmtp-smtp-corp-main-69.vla.yp-c.yandex.net (mail-nwsmtp-smtp-corp-main-69.vla.yp-c.yandex.net [IPv6:2a02:6b8:c1f:3a87:0:640:845c:0]) by forwardcorp1a.mail.yandex.net (Yandex) with ESMTPS id A301FC01AA; Sat, 14 Feb 2026 20:41:55 +0300 (MSK) Received: from smtpclient.apple (unknown [2a02:6bf:8080:d74::1:2f]) by mail-nwsmtp-smtp-corp-main-69.vla.yp-c.yandex.net (smtpcorp/Yandex) with ESMTPSA id rfatXu1AtGk0-naTR8Oz9; Sat, 14 Feb 2026 20:41:55 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex-team.ru; s=default; t=1771090915; bh=5HVx9TaTVhMT2wyqXbpqKjERf9I2/VDdlRRlPYpprjE=; h=Message-Id:To:Date:References:Cc:In-Reply-To:From:Subject; b=W0Z0VOOaCIa4Sma/zFVSLt2NJNMlG/bUoBLs7vT33xme8m5wIK0YMR/TlO1pXC1sd XsSchgbq8UIzdnzyh6AyuVNhxwNf6QCY7MWqpxdU7jWQZxIF0MPBnutSAwc4nKo+UM qCiMheXyAidts+BnyWfZSDsa8fT9VDFNFMwM78dc= Authentication-Results: mail-nwsmtp-smtp-corp-main-69.vla.yp-c.yandex.net; dkim=pass header.i=@yandex-team.ru Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.300.41.1.7\)) Subject: Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction" From: Andrey Borodin In-Reply-To: Date: Sat, 14 Feb 2026 22:41:43 +0500 Cc: Sebastian Webber , pgsql-bugs@lists.postgresql.org, Andrey Borodin , =?utf-8?Q?=C3=81lvaro_Herrera?= , Dmitry Yurichev , Chao Li , Ivan Bykov , Kirill Reshke Content-Transfer-Encoding: quoted-printable Message-Id: References: <349f9c82-3a8b-48ad-8cc4-fe81553793dd@iki.fi> To: Heikki Linnakangas X-Mailer: Apple Mail (2.3864.300.41.1.7) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 14 Feb 2026, at 21:18, Andrey Borodin wrote: >=20 > Perhaps, we also can bump latest_page_number forward? This is not a good idea, we don't want "most accurate = latest_page_number", we need precise number at any point after = StartupMultiXact(). Wiping write by XLOG_MULTIXACT_TRUNCATE_ID seems correct to me = everywhere 14-18. I'd also suggest updating comment: * this is not critical data, since we use it only to avoid swapping out * the latest page. It's absolutely critical now. Best regards, Andrey Borodin.=