3 ms·

I don't really understand why people went with this headline and not "PostgreSQL developers discover most programs have used fsync incorrectly for decades, incl

• macdice 8y ago
  I agree, the initial report on pgsql-hackers had a subject that blamed PostgreSQL too strongly and I think that carried through to articles and blogs and Twitter etc. You are right, this affects other things too. And indeed several projects took action to remove any notion of fsync retry, referencing the LWN article etc. POSIX is probably underspecified. AN Austin Group defect report would be interesting...
• giovannibajo1 8y ago
  Because most normal programs do open-write-sync-close, and that mostly works as expected. Postgres does open-write-close and then later, in another unrelated process, open-fsync-close. They discovered this doesn’t always work, because if somebody somewhere does a fsync on that file for any reason, their process might miss the error as it doesn’t stick.
• howard941 8y ago
  It's too long by 26 characters?