{"id":"critical-wal-operations-always-force-fsync","text":"Checkpoints, batch commits, and segment rotations all bypass the configured sync mode by calling fsync unconditionally, creating a two-tier durability model where structural WAL operations are always durable even when individual record writes are not.","truth_value":"IN","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["wal-checkpoint-forces-fsync","wal-batch-always-fsyncs","rotation-always-fsyncs","force-true-bypasses-sync-mode"],"outlist":[],"label":"Four beliefs establish that force=True fsync is consistently applied at WAL state-transition boundaries but not at individual write boundaries"}],"dependents":["fsync-policy-inconsistent-across-critical-paths","wal-durability-effective-on-standards-compliant-fsync"],"metadata":{"last_reviewed":"2026-05-30T09:01:17","review_result":"unnecessary"},"created_at":"","updated_at":"","reviewed_at":"","verified_at":"","retracted_at":"","explanation":{"steps":[{"node":"critical-wal-operations-always-force-fsync","truth_value":"IN","reason":"SL justification valid","antecedents":["wal-checkpoint-forces-fsync","wal-batch-always-fsyncs","rotation-always-fsyncs","force-true-bypasses-sync-mode"],"label":"Four beliefs establish that force=True fsync is consistently applied at WAL state-transition boundaries but not at individual write boundaries"},{"node":"wal-checkpoint-forces-fsync","truth_value":"IN","reason":"premise"},{"node":"wal-batch-always-fsyncs","truth_value":"IN","reason":"premise"},{"node":"rotation-always-fsyncs","truth_value":"IN","reason":"premise"},{"node":"force-true-bypasses-sync-mode","truth_value":"IN","reason":"premise"}]}}