3 ms·
I think it's worthwhile to note that this, even before both kernel and postgres changes, really only is an issue if there are very serious storage issues, commo
by anarazel 8y ago
I think it's worthwhile to note that this, even before both kernel and postgres changes, really only is an issue if there are very serious storage issues, commonly causing more corruption than just forgetting the data due to be fsynced. The kernel has its own timeout / retry logic and if those retries succeed, there's no issue. Additionally, most filesystems remount read-only if there's any accompanying journaling errors, and in a lot of cases PG IO will also have a metadata effect.
- waz0wski 8y agoi/o errors are an ongoing issue for AWS M5 and C5 instance types with their cloudy nvme devices, they have a tendency to randomly disappear or have extended timeouts https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788035 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788035 unfortunately the upstream patches being backported don't provide any real write guarantee