Bintrail: MySQL Time-Travel Queries Using Indexed Binlogs

2026-05-21 · Source: InfoQ · Field: Technology & Digital — Software Development & Engineering, Data Science & Analytics, Cloud Computing & IT Infrastructure · Depth: Intermediate, short

Summary

Bintrail, a new layer introduced on May 21, 2026, brings point-in-time queries and row-history lookups to MySQL, a major relational database previously lacking native temporal querying. It achieves this by indexing MySQL ROW-format binary logs and routing queries through ProxySQL, all without modifying MySQL or application code. Bintrail supports "AS OF" and "BETWEEN" time-travel queries, enabling users to query data as of a past timestamp or review change history for recovery and audit. It parses binlogs, indexes row events with before/after images, and generates reversal SQL. The system maintains an independent indexed history store, allowing queries to span longer periods and extend into archived Parquet data on S3. Available on GitHub under BUSL, Bintrail currently supports literal timestamp queries, primary-key lookups, and capped full-table restores.

Key takeaway

For Data Engineers managing MySQL instances, Bintrail offers a critical solution for historical data access and recovery. If you need to perform point-in-time restores or audit row-level changes without complex binlog replay, consider integrating Bintrail. This allows you to query past data states directly. It significantly reduces recovery time and risk in environments with increasing automation and rapid operational changes. Evaluate its BUSL license and current limitations regarding joins and complex filtering.

Key insights

MySQL can gain native-like time-travel and row-history querying capabilities without core modifications, using indexed binlogs and ProxySQL.

Principles

• MySQL lacks native temporal querying.
• Binlogs offer a source for historical data.
• External layers can extend database functionality.

Method

Bintrail parses MySQL ROW-format binlogs, indexes row events with before/after images, generates reversal SQL, and routes "AS OF"/"BETWEEN" queries via ProxySQL to its history store.

In practice

• Query data as of a past timestamp.
• Review row-level change history.
• Recover from data incidents precisely.

Topics

• MySQL
• Time-Travel Queries
• Binlog Indexing
• ProxySQL
• Data Recovery
• Data Auditing

Code references

• dbtrail/bintrail

Best for: CTO, VP of Engineering/Data, Product Manager, Data Engineer, Software Engineer, MLOps Engineer

Related on AIssential

• MySQL 9.6 Changes Foreign Key Constraints and Cascade Handling — MySQL 9.6 moves foreign key cascade handling to the SQL layer, improving data consistency for replication.
• The Undo Button for Big Data: An Intro to Delta Lake Time Travel — Delta Lake's transaction log enables data time travel, providing an undo button for big data operations.
• Netflix Serves 84% of Query Results from Cache with Interval-Aware Caching in Apache Druid — Decomposing query results into time-aligned segments enables high cache reuse for rolling window analytics.
• 500 Blog Posts To Learn About Database — This compilation offers 500 HackerNoon blog posts, ordered by reader engagement, providing extensive knowledge on "Database" technologies.
• Snapshot Tables in Analytics: The Complete Guide from Basics to Advanced — Snapshot tables capture historical data states, enabling time-based analysis beyond current data.
• I Found 487 GB Of Data Nobody Had Looked At In Three Years. Deleting It Felt Like Archaeology. — Regular storage audits can identify dormant data, reducing costs and improving database efficiency.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by InfoQ.