News for hackers. Stuff that matters.
Re:Tailscale Traces Database Corruption to 16y/o SQLite WAL-... by q3k on Wednesday August 12, 2026 @08:55PM (#49280546)
Yeah, I also feel 'just use SQLite [no matter what]' is just the pendulum swinging hard after the 'just use mongodb [no matter what]' of yesteryear.

It's so sometimes just performative. I remember when Tailscale had a similar performative approach with 'just use a JSON file on disk'. Then etcd. Then SQLite. Like sure, you can keep picking the absolite mininum technology for your needs and then change it every couple of years... Or you could just immediately go with a solid Postgres (or Postgres-like setup, eg. yugabyte) and save yourself a bunch of faffing about with weird solutions and migrating between them. But I guess that doesn't drive engagement on your blog.

Re:Tailscale Traces Database Corruption to 16y/o SQLite WAL-... by sealeck on Wednesday August 12, 2026 @09:54PM (#49280969)
Postgres has also had pretty serious bugs, eg fsyncgate
Re:Tailscale Traces Database Corruption to 16y/o SQLite WAL-... by lima on Saturday August 15, 2026 @02:07PM (#49312809)
There's also the more fundamental issue that Postgres - unlike something like Yugabyte - does not use a distributed consensus algorithm for writes and can lose committed writes during network partitions.

But of course, neither does Tailscale's weird DIY contraption.