| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | Sebastian Webber <sebastian(at)swebber(dot)me>, pgsql-bugs(at)lists(dot)postgresql(dot)org, Andrey Borodin <amborodin(at)acm(dot)org>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Dmitry Yurichev <dsy(dot)075(at)yandex(dot)ru>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, Ivan Bykov <i(dot)bykov(at)modernsys(dot)ru>, Kirill Reshke <reshkekirill(at)gmail(dot)com> |
| Subject: | Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction" |
| Date: | 2026-02-14 17:41:43 |
| Message-ID: | ACB73592-44AB-40EB-85F6-19A00184D29F@yandex-team.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On 14 Feb 2026, at 21:18, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
>
> 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2026-02-14 19:07:22 | Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16 |
| Previous Message | Andrey Borodin | 2026-02-14 16:18:39 | Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction" |