How Tailscale helped find the SQLite WAL-Reset bug
tailscale.com · 2,890 words · saved by 1 readers
Tailscale and SQLite developers traced maddening corruption incidents to find the WAL-Reset data race, then uncovered a second stale expression index bug.
At the end of last year, our uptime was pretty shaky. You can see this trend on our status page, and that instability continued into the new year. Many of these outages were caused by a single bug, deep in SQLite. It took months of intense forensics to track it down. Now we’re in summer, we’re confident that we’ve found the bug, that we understand it—and more importantly, that we’ve fixed it. We know our customers expect Tailscale to be a reliable service, and for several months we didn’t live up to that promise. That’s disruptive, and we’re sorry. We’re publishing this blog post to…
saved by
related reading
- How To Corrupt An SQLite Database Filesqlite.org
- Agent swarms and the new model economics · Cursorcursor.com
- Building data-centric apps with a reactive relational databaseriffle.systems
- Wesley Aptekar-Cassels | Consider SQLiteblog.wesleyac.com
- How Does a Database Work?cstack.github.io
- Tailscale: How it workstailscale.com
- I'm All-In on Server-Side SQLite · The Fly Blogfly.io
- Scaling PostgreSQL to power 800 million ChatGPT users | OpenAIopenai.com
- Patching the PostgreSQL JDBC Driverengineering.zalando.com
- Hōrōshi バガボンド (@KatanaLarp) on Xx.com
- Write-Ahead Loggingsqlite.org
- Against SQLscattered-thoughts.net