Re:Fsyncgate: Errors on fsync are unrecoverable (2018)
by macdice on Monday July 22, 2019 @03:33AM
(#20495967)
I think the problem is mostly ENOSPC from fsync() which jettisons data just like EIO on Linux. If you ran out of space, PostgreSQL would only learn about that while checkpointing, and then retry and carry on. Boom, data loss. Today PostgreSQL would panic on the first ENOSPC from fsync() so the problem is mostly "fixed".
Re:Fsyncgate: Errors on fsync are unrecoverable (2018)
by cyphar on Sunday July 21, 2019 @08:44PM
(#20494648)
The main thing to keep in mind is that NFS exercises a bunch of VFS code paths that effectively no other filesystems touches. So you are more at risk to strange VFS bugs, as well as general NFS shenanigans, which other PG users may not have seen before.
You're right though: you really do want to have some idea what you're doing, if you're going to go there.
Source: my day job is PostgreSQL DBA, and has been for ~15 years now.
EDIT: Phrasing.