From: | Casey Shobe <casey(dot)allen(dot)shobe(at)icloud(dot)com> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Issues with blocksize smaller than 8KB |
Date: | 2025-10-17 15:42:12 |
Message-ID: | C5DC82D6-C76D-4E8F-BC2E-DF03EFC4FA24@icloud.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
I have been comparing performance of postgresql (18.0) compiled for various block sizes etc., and found that while 8kb and 16kb builds work fine, a 4kb build does not, with identical configuration. When I try to initialize pgbench, --scale=10 works fine, but the --scale=100 I was trying and even just --scale=20 result in a long delay on the vacuum analyze step followed by Postgres crashing due to a segmentation fault.
I also found that initdb fails when I compile for a blocksize of either 1KB or 2KB build:
2025-10-17 15:39:13.182 UTC [97433] DETAIL: The database cluster was initialized with RELSEG_SIZE 1895825408, but the server was compiled with RELSEG_SIZE 1895825408.
2025-10-17 15:39:13.182 UTC [97433] HINT: It looks like you need to recompile or initdb.
- Casey
From | Date | Subject | |
---|---|---|---|
Next Message | Yuri Zamyatin | 2025-10-17 20:09:00 | Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade |
Previous Message | Amit Langote | 2025-10-17 10:36:43 | Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift) |