Re: Does larger i/o size make sense?

> The big-picture problem with work in this area is that no matter how you
> do it, any benefit is likely to be both platform- and workload-specific.
> So the prospects for getting a patch accepted aren't all that bright.

Indeed.

Would it make sense to have something easier to configure that recompiling 
postgresql and managing a custom executable, say a block size that could 
be configured from initdb and/or postmaster.conf, or maybe per-object 
settings specified at creation time?

Note that the block size may also affect the cache behavior, for instance 
for pure random accesses, more "recently accessed" tuples can be kept in 
memory if the pages are smaller. So there are other reasons to play with 
the blocksize than I/O access times, and an option to do that more easily 
would help.

-- 
Fabien.