Re: IPC/MultixactCreation on the Standby server - Mailing list pgsql-hackers

From Andrey Borodin
Subject Re: IPC/MultixactCreation on the Standby server
Date
Msg-id 703E24ED-2E31-41E5-93FD-A48F3D8B70F2@yandex-team.ru
Whole thread Raw
In response to Re: IPC/MultixactCreation on the Standby server  (Maxim Orlov <orlovmg@gmail.com>)
Responses Re: IPC/MultixactCreation on the Standby server
List pgsql-hackers

> On 5 Dec 2025, at 21:36, Maxim Orlov <orlovmg@gmail.com> wrote:
>
> It's good that the test was added. But it seems like it could be
> improved a bit. The problem is, it only runs successfully with a
> standard block size. Plus, the comment about the number of bytes was a
> bit unclear, for my taste. PFA patch, it should make this test pass
> with different block sizes.

Oh, great catch!

Other tests seem to extract block size using database query like

$primary->safe_psql('postgres',
"SELECT setting::int FROM pg_settings WHERE name = 'block_size';");
or
$blksize = int($node->safe_psql('postgres', 'SHOW block_size;'));

But here we do not have running cluster, so resorting to parsing pg_resetwal seems reasonable.

Thanks!


Best regards, Andrey Borodin.


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: apply_scanjoin_target_to_paths and partitionwise join
Next
From: Andrey Borodin
Date:
Subject: Re: Tighten up range checks for pg_resetwal arguments