From: Casey Shobe <casey.allen.shobe@icloud.com>
To: pgsql-bugs@lists.postgresql.org
Subject: Issues with blocksize smaller than 8KB
Date: Fri, 17 Oct 2025 11:42:12 -0400
Message-ID: <C5DC82D6-C76D-4E8F-BC2E-DF03EFC4FA24@icloud.com> (raw)
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: casey.allen.shobe@icloud.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Issues with blocksize smaller than 8KB
In-Reply-To: <C5DC82D6-C76D-4E8F-BC2E-DF03EFC4FA24@icloud.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox