At least Linux had one problem: fsync() syncs the inode to disk, but not the directory entry: if you rename a file, open it, write to it, fsync, and the computer crashes, then it's not guaranteed that the file rename is on the disk.I'm assuming fsync syncs writes issued by other processes on the same file,It was already pointed out that we can't rely on that assumption.
which isn't necessarily true though.
So the NetBSD and Sun developers I checked with both asserted fsync does in
fact guarantee this. And SUSv2 seems to back them up:
I think only the old ext2 is affected, not the journaling filesystems.
-- Manfred
---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives?
http://archives.postgresql.org
