| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Maxim Orlov <orlovmg(at)gmail(dot)com> |
| Cc: | Á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 21:39:49 |
| Message-ID: | 1dc70311-9339-4ed1-9347-6c00fc889831@iki.fi |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/12/2025 20:36, Andrey Borodin wrote:
>> On 5 Dec 2025, at 21:36, Maxim Orlov <orlovmg(at)gmail(dot)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.
+1, pg_resetwal makes sense here. Calculating the filename of the last
SLRU segment also needs to be adjusted. It was hardcoded to FFFF, but
it's different with other block sizes.
Fixed that and committed. Thanks!
P.S. I'm surprised we don't have any buildfarm members with non-default
block sizes.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Previous Message | Bryan Green | 2025-12-05 21:24:46 | Re: [PATCH] Allow complex data for GUC extra. |