News for hackers. Stuff that matters.
Re:PostgreSQL's fsync surprise by ajross on Wednesday May 02, 2018 @09:49PM (#16982740)
> what a mess doing what seem like simple file operations is

Proper handling and reporting of hardware-level errors all the way up through the stack (driver, block layer, filesystem, C library) to the application so it can recover in a reliable way is not a simple operation!

Simple operations are open/close/read/write. Those work. Until they don't, then you need to know how far back the operations you already did and "assumed" had worked didn't. And in this case the promise made to PostgreSQL by fsync() wasn't as firm as the "obvious" interpretation of the documentation would lead one to believe.

Re:PostgreSQL's fsync surprise by dagenix on Wednesday May 02, 2018 @11:35PM (#16983171)
I don't doubt its a hard problem. If there was a simple, obvious better way to do it, I imagine we'd have it by now.