| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Failing test_aio tests due to too low(illegal?) segsize_blocks |
| Date: | 2026-04-08 18:57:01 |
| Message-ID: | ym373n5ssebp64n7kwk4cwx2d5epwbabm76pdrk3gat63fxwbd@knjuyj6coe27 |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2026-04-08 08:51:30 +0200, Jakub Wartak wrote:
> For some reason I've ended up using -Dsegsize_blocks=4 and I've started
> getting ninja test errors after getting back from vacation leave like
> below (so this test was included only since then):
It's IIRC not the only test that fails if you do that.
> .cirrus file show usage of segsize_blocks=6, and also 8 works fine without
> errors, so it's just nuisance on my side, but it took some minutes for me
> to realize this and I'll just ask maybe we should just block usage of
> RELSEG_SIZE < 6 blocks in meson/configure? (patch attached)
-1. I find it quite useful for testing some edge cases to be able to
configure with less.
If you really care, I'd be ok with a patch that makes the relevant test_aio
tests errors out with if it's set to a too low value...
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2026-04-08 19:09:48 | Re: Add pg_stat_autovacuum_priority |
| Previous Message | Tom Lane | 2026-04-08 18:53:20 | Re: Add pg_stat_autovacuum_priority |