News for hackers. Stuff that matters.

A comment on Devious SQL: Message Queuing Using Native PostgreSQL. Parent comment

Re:Devious SQL: Message Queuing Using Native PostgreSQL by eloff on Friday January 28, 2022 @08:47PM (#30122938)
It has complex failure modes though, unless you're not at all concerned about what happens if the program crashes, power goes out, file gets corrupted, etc.

It's surprisingly difficult to write something that stores changing data on disk correctly and durably.

[ Parent | on HN ]
Re:Devious SQL: Message Queuing Using Native PostgreSQL by 00000000005 on Friday January 28, 2022 @10:41PM (#30123561)
Databases have the same problems when disks fail, power goes out etc.
[ Parent | on HN ]
Re:Devious SQL: Message Queuing Using Native PostgreSQL by eloff on Saturday January 29, 2022 @11:48AM (#30127815)
If you mean they have to solve the same problems with very careful design and programming, yes. It's non trivial. Even Postrgres had a correctness issue around fsync for nearly twenty years.

If you roll your own, that's very hard to get right. I wouldn't have confidence in such a system that I've built myself.

[ Parent | on HN ]