Re: IPC/MultixactCreation on the Standby server

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Dmitry Yurichev <dsy(dot)075(at)yandex(dot)ru>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Ivan Bykov <i(dot)bykov(at)modernsys(dot)ru>, Kirill Reshke <reshkekirill(at)gmail(dot)com>
Subject: Re: IPC/MultixactCreation on the Standby server
Date: 2025-12-05 18:50:17
Message-ID: D8AAAC6D-3ACB-4A07-8EB5-F81CB661B5A6@yandex-team.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 4 Dec 2025, at 19:17, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
>
> I tried to modify the new wraparound TAP test to reproduce that, but it turned out to be difficult because you need to have multiple backends assigning multixids concurrently to hit that.

IIUC, new TAP test verifies multixact Id wraparound (-m key in pg_resetwal).
While the bug was in multixact offsets wraparound.

I'm on-call for the rest of this week, but a bit later I can produce fast tests for all kinds of wraparounds :)

But as you said, hopefully soon there won't be wraparounds, and, what's more important, offsets\members space exhaustion.

Best regards, Andrey Borodin.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kirill Reshke 2025-12-05 19:56:22 Re: vacuumdb: add --dry-run
Previous Message Sami Imseih 2025-12-05 18:49:59 Re: Proposal: Add a callback data parameter to GetNamedDSMSegment