Status: OUT
The codebase has a systematic fsync policy inconsistency between components: WAL critical operations (checkpoints, batch commits, segment rotations) always force-fsync regardless of configured mode, but B-tree metadata mutations (which are equally critical for crash recovery) skip fsync entirely despite paying double fsync for user data pages.
WAL forces fsync for structural operations while B-tree skips it for equally critical metadata
Depends on (SL): critical-wal-operations-always-force-fsync, btree-mutation-fsync-is-asymmetric