Re: Regression failures after changing PostgreSQL blocksize - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Regression failures after changing PostgreSQL blocksize
Date
Msg-id aY4n_jPsNrfmPkSE@alap3.anarazel.de
Whole thread Raw
In response to Re: Regression failures after changing PostgreSQL blocksize  (Yasir <yasir.hussain.shah@gmail.com>)
List pgsql-hackers
Hi,

On 2026-02-13 00:18:39 +0500, Yasir wrote:
> Thank you all for providing invaluable information. Based on the answers,
> it's clear that regression failures with custom block sizes are expected
> and not necessarily indicative of functional bugs.
> However, it creates doubts, so, can we add alternative test output files
> for the changes caused by different block sizes? E.g: the attached poc
> patch. Whether such an approach would be acceptable?

No. That'd require everyone modifying these tests to test with multiple block
sizes. That'd almost certainly be forgotten and the alternative files would
get out of date. And if not forgotten, it's extra work for pretty much no
gain.


> Which other compile time options are expected to cause test failures?

I know of one: Using an extremely small --with-segsize-blocks (less than
something like 6 or 8 blocks) causes some test failures.  There are some
pg_config_manual.h and a lot more other defines that, if changed, would also
cause "spurious" test failures.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: proposal: schema variables
Next
From: Andres Freund
Date:
Subject: Re: Odd usage of errmsg_internal in bufmgr.c