Re: IPC/MultixactCreation on the Standby server

Dmitry <dsy.075@yandex.ru>

From: Dmitry Yurichev <dsy.075@yandex.ru>

To: Heikki Linnakangas <hlinnaka@iki.fi>, Andrey Borodin <x4mmm@yandex-team.ru>

Cc: Álvaro Herrera <alvherre@kurilemu.de>, pgsql-hackers@lists.postgresql.org, Ivan Bykov <i.bykov@modernsys.ru>, Kirill Reshke <reshkekirill@gmail.com>

Date: 2025-12-03T14:19:37Z

Lists: pgsql-hackers

On 12/2/25 16:48, Heikki Linnakangas wrote:
> Thanks! Agreed, v14-16 were the same. v17 and v18 might be worth testing 
> separately, to make sure I didn't e.g. screw up the locking differences.

I tested on the REL_18_1 tag (with applying 
v15-pg18-0001-Set-next-multixid-s-offset-when-creating-a-.patch).
I didn't notice any deadlocks or other errors. Thanks!

-- 
Best regards,
Dmitry Yurichev.

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