> But database engines are absolutely the target of io_uring's feature set and they're expected to be managing this complexity. io_uring includes an fsync opco

> But database engines are absolutely the target of io_uring's feature set and they're expected to be managing this complexity. io_uring includes an fsync opcode (with range support). When folks talk about fsync generally here, they're not saying the io_uring is unusable, they're saying that they'd expect the fsync to be used whether it's via the io_uring opcode, the system call, or some other mechanism yet to be created.