Re: IPC/MultixactCreation on the Standby server

Andrey Borodin <x4mmm@yandex-team.ru>

View thread

From: Andrey Borodin <x4mmm@yandex-team.ru>

To: Álvaro Herrera <alvherre@kurilemu.de>

Cc: Dmitry <dsy.075@yandex.ru>, pgsql-hackers@lists.postgresql.org

Date: 2025-07-28T12:49:32Z

Lists: pgsql-hackers

Attachments

v8-PG17-0001-Avoid-edge-case-2-in-multixacts.patch (application/octet-stream) patch v8-0001
v8-0001-Avoid-edge-case-2-in-multixacts.patch (application/octet-stream) patch v8-0001

> On 27 Jul 2025, at 16:53, Andrey Borodin <x4mmm@yandex-team.ru> wrote:
> 
> we have to do this "next offset" dance on Primary too.

PFA draft of this.
I also attach a version for PG17, maybe Dmitry could try to reproduce the problem with this patch. I think the problem should be fixed by the patch.

Thanks!

Best regards, Andrey Borodin.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix test to work with non-8kB block sizes
- 7c2061bdfba7 19 (unreleased) landed
Fix setting next multixid's offset at offset wraparound
- 48969555447f 14.21 landed
- b9a02b9780bc 15.16 landed
- 4d689a17693e 16.12 landed
- cad40cec24f3 17.8 landed
- 02ba5e3be4f3 18.2 landed
- 4d936c3fff1a 19 (unreleased) landed
Add test for multixid wraparound
- 7b81be9b4267 19 (unreleased) landed
Set next multixid's offset when creating a new multixid
- 81416e1016dd 14.21 landed
- 8cfb174a61eb 15.16 landed
- 635166913078 16.12 landed
- 8ba61bc06386 17.8 landed
- e46041fd973c 18.2 landed
- 789d65364cde 19 (unreleased) landed
psql: Improve tab completion for large objects.
- 14ee8e640300 19 (unreleased) cited
Refactor some repetitive SLRU code
- c61678551699 19 (unreleased) cited
Transaction IDs wrap around, per my proposal of 13-Aug-01. More
- bc7d37a525c0 7.2.1 cited