DBTrail lets you use InnoDB and DuckDB for the same tables at the same time. You don’t have to pick a storage engine for each table: your tables are in both, and DBTrail keeps them in sync, minutes behind, like a replica.
https://t.co/Psm7dg5bhb
¡Ya arrancó!
📣 @dbtrail_ nos presenta 💬 "Poor man's lakehouse: analytics históricas y recovery sobre MySQL con DuckDB + Parquet"
📍 Sala Abasto
Seguí el vivo https://t.co/9u7uz4CJtj
#Nerdearla 🇦🇷
MySQL Ecosystem Tool Spotlight
We’re highlighting useful tools and projects across the MySQL ecosystem to make them easier to discover. Today: @dbtrail_ - a time machine for MySQL created by @clickslash#MySQL#OpenSource#OurSQLFoundation
Every recovery tool makes the same promise: if something goes wrong, it will give your data back exactly as it was.
DB Trail does not ask for your trust. This post is about how it checks that the recovery would be correct.
https://t.co/YQCnsjSw6W
Want to add flow-control to you MySQL cluster without migrating? use Bintrail from @dbtrail_ add @proxysql and you have yourself a cluster with flow control without migrating to Galera Cluster or Group Replication
https://t.co/Pn5oSZIstD
#MySQL
MariaDB stores row history inside your hot table and never expires it. Lighter path: the binlog already is your append-only history. Just externalize it.
MySQL time travel. History lives in the binlog, lands as Parquet, reads from DuckDB. Details here:
https://t.co/eJ1twZqW5w
I am honored to present MyVector at the Oracle @MySQL Contributor Summit 2026 as a contributor, a MySQL Rockstar, and an Oracle ACE Pro.
Stay tuned for more... https://t.co/eVQDIisAni
PostgreSQL Internals for the MySQL DBA
PostgreSQL internals explained from the perspective of someone who already knows MySQL. Every concept mapped to its InnoDB equivalent. No fanboy energy. Just the architecture.
https://t.co/zdynw32fx9
@InfoQ covered Bintrail, a project bringing time-travel style queries to MySQL using indexed binary logs.
ProxySQL plays an interesting role in the architecture: normal MySQL traffic goes to MySQL, while _flashback, _diff, and _snapshot queries can be routed to the Bintrail shim.
A practical example of ProxySQL as a programmable routing layer for MySQL infrastructure.
https://t.co/DTpJ3LZIeE
Interesting @InfoQ piece by Renato Losio on Bintrail, created by Daniel Guzman-Burgos (@clickslash) .
MySQL has binlogs, but parseable history is not the same as queryable history.
The clever part: Bintrail can sit behind ProxySQL, with ProxySQL routing _flashback / _diff queries to the shim while normal traffic keeps going to MySQL.
A nice example of the proxy layer enabling new database capabilities without changing the application.
https://t.co/Qfu6WaJAfF
@InfoQ covered Bintrail, a project bringing time-travel style queries to MySQL using indexed binary logs.
ProxySQL plays an interesting role in the architecture: normal MySQL traffic goes to MySQL, while _flashback, _diff, and _snapshot queries can be routed to the Bintrail shim.
A practical example of ProxySQL as a programmable routing layer for MySQL infrastructure.
https://t.co/DTpJ3LZIeE