Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> In the case of a performance-critical file like the WAL that's always read
> sequentially it may be to our advantage to defeat this technique and force it
> to be allocated sequentially. I'm not sure whether any filesystems provide any
> option to do so.
We more or less do that already by filling the entire file in one go
when it's created ...
regards, tom lane