MySQL Time-Travel with near-ZERO overhead: How bintrail skips the write load
Four operations questions about Time Travel SQL: multi-TB tables, retention, monitoring and partitioning.
Archive
Time-travel SQL for MySQL, finally
MySQL was the only major OLTP database without time-travel queries. Here is how that gap closes, with no fork and no ALTER TABLE storm.
For a Database, survive used to mean “The server stays up”. With AI Agents, that’s not enough anymore
Survive used to be physical: disk, memory, replication. With agents that definition is too small. Five things change.
An AI Agent is talking to your MySQL. And the database doesn’t know who is that! – Agent Era, Part 3
Something deleted thirty thousand rows overnight, and the binlog only says app_user. MySQL cannot tell who the agent is.
Three Promises in the Agent Era, Part 2: Agents on production MySQL are fine. Until they’re not.
Sooner or later you will recover data because of something an agent did. The three most common shapes that day takes.
Three Promises in the Agent Era, Part 1: The Frame, Reread
A database makes three promises: it executes queries, manages relationships, and survives its machine. Reread for the agent era.