News for hackers. Stuff that matters.
Re:PostgreSQL's fsync surprise by teddyh on Thursday May 03, 2018 @03:11AM (#16983946)
> Modern filesystems straight out expose the wrong API for 99% of applications. App developers almost never think of data as a stream of bytes. We think of data as a set of records

As I recall, older operating systems like VMS and MULTICS all did this, and it was all tremendously complex. Unix’ simple stream-of-bytes file abstraction was a reaction to this, and it worked so well that it became the prevailing model. Before doing again what didn’t work before, check up on why it failed the previous time.

Re:PostgreSQL's fsync surprise by davidgould on Thursday May 03, 2018 @08:29PM (#16991219)
Unix is older than VMS (source: programmed on VMS when it was new), so it is unlikely that the unix file abstraction is a reaction to VMS.
Re:PostgreSQL's fsync surprise by orev on Friday May 04, 2018 @10:16PM (#16999961)
Mainframes came before all of them and they used the records model.
Re:PostgreSQL's fsync surprise by gaius on Thursday May 03, 2018 @04:15AM (#16984202)
Your recollection is faulty; RMS was an absolute pleasure to work with. Fast, clean and efficient, and concurrent access was pain-free too. RMS supported streams as well as records.

Others have mentioned SQLite as replacement for fopen()... that’s a fairly RMS-like experience on modern systems

(I wonder if this is being downvoted because people think RMS means Stallman)

Re:PostgreSQL's fsync surprise by jordanb on Thursday May 03, 2018 @08:07AM (#16985185)
I think you guys are arguing worse is better versus the right thing. :)

Unix made for very simple filesystem internals, with a crappy interface (worse is better). RMS was a very complicated filesystem with a nice interface (the right thing).

Re:PostgreSQL's fsync surprise by davidgould on Thursday May 03, 2018 @08:34PM (#16991249)
RMS was an absolute pleasure to work with. Fast, clean and efficient, and concurrent access was pain-free too. RMS supported streams as well as records.

Hummmph, it was kind of a pleasure on a VAX, but on a PDP-11 under RSX or RSTS/E the libraries for it ate so much of the (16 bit) address space that it became a real challenge to fit a useful application into memory.

Also, it only sort of supported streams, they were not really byte streams like Unix, but variable length record streams with CRLF marking the record delimiters. So porting Unix code to VMS was never quite as straightforward as one hoped.