Re: IPC/MultixactCreation on the Standby server

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: Dmitry <dsy(dot)075(at)yandex(dot)ru>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: IPC/MultixactCreation on the Standby server
Date: 2025-07-21 14:58:47
Message-ID: 34D6F55B-31DB-49E6-81ED-3ABEC3428FBE@yandex-team.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 18 Jul 2025, at 18:53, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
>
> Please find attached dirty test and a sketch of the fix. It is done against PG 16, I wanted to ensure that problem is reproducible before 17.

Here'v v7 with improved comments and cross-check for correctness.
Also, MultiXact wraparound is handled.
I'm planning to prepare tests and fixes for all supported branches, if there's no objections to this approach.

Best regards, Andrey Borodin.

Attachment Content-Type Size
v7-0001-Test-that-reproduces-multixat-deadlock-with-recov.patch application/octet-stream 6.3 KB
v7-0002-Fill-next-multitransaction-in-REDO-to-avoid-corne.patch application/octet-stream 4.4 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jiří Kavalík 2025-07-21 15:19:17 Fwd: [PATCH] Support for basic ALTER TABLE progress reporting.
Previous Message Andrei Lepikhov 2025-07-21 14:55:45 Re: track generic and custom plans in pg_stat_statements