3 ms·
I did not investigate MySQL code (or other product) but I would be very surprised if PostgreSQL is the only one impacted by this issue.
by Manozco 8y ago
I did not investigate MySQL code (or other product) but I would be very surprised if PostgreSQL is the only one impacted by this issue.
- ausjke 8y agoby reading the lwn article it seems postgresql is hit especially hard per its design and "heavy" use of fsync, I have yet to find similar impact on mysql.
- olavgg 8y agoAll SQL databases are "heavy" users of fsync. Though, this problem is not relevant on FreeBSD nor Illumos. Error handling for a operating system is really complex stuff. I'm surprised that this isn't working properly, fsync is not about speed, but reliability. Userland applications expect it to work and behave as intended.
- ausjke 8y agothe key is error reporting
- macdice 8y agoYes that seems unlikely. Almost all Unix software uses buffered IO, including several other databases or database-like things including package managers, DNS servers, mail servers, ..., and MySQL does too by default. It even uses it when you choose O_DIRECT (though I'm not sure if that's exposed to write-back error eating risk or not). That said, as several people have said, this is a very unlikely failure mode. When filesystems die, you know about it. The type of transient failure required to lose data this way is quite unlikely.