public inbox for [email protected]  

help / color / mirror / Atom feed

From: Andrey Borodin <[email protected]>
To: Heikki Linnakangas <[email protected]>
Cc: Sebastian Webber <[email protected]>
Cc: [email protected]
Cc: Andrey Borodin <[email protected]>
Cc: Álvaro Herrera <[email protected]>
Cc: Dmitry Yurichev <[email protected]>
Cc: Chao Li <[email protected]>
Cc: Ivan Bykov <[email protected]>
Cc: Kirill Reshke <[email protected]>
Subject: Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"
Date: Sat, 14 Feb 2026 21:18:39 +0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CACV2tSw3VYS7d27ftO_cs+aF3M54+JwWBbqSGLcKoG9cvyb6EA@mail.gmail.com>
	<[email protected]>

Ouch...

I remember this place. For some reason I thought endTruncOff is the end of offsets. That would make sense here... Now I see it's just a new oldest offset.

> On 14 Feb 2026, at 16:42, Heikki Linnakangas <[email protected]> wrote:
> 
> If we want to play it even more safe -- and I guess that's the right thing to do for backpatching -- we could set latest_page_number *temporarily* while we do the the truncation, and restore the old value afterwards.

As far as I can see, the only relevant usage of last_page_number is:
/*
 * While we are holding the lock, make an important safety check: the
 * current endpoint page must not be eligible for removal.
 */
if (ctl->PagePrecedes(shared->latest_page_number, cutoffPage))
{
	LWLockRelease(shared->ControlLock);
	ereport(LOG,
		(errmsg("could not truncate directory \"%s\": apparent wraparound",
		ctl->Dir)));
	return;
}


Perhaps, we also can bump latest_page_number forward?


Best regards, Andrey Borodin.

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox