Loading feed…
Planet MySQL0 Hot0 comments7 min read
Replicating from InnoDB into a DuckDB storage engine
Percona tested feeding an InnoDB MySQL primary's row-based replication into a replica where tables use the experimental DuckDB storage engine, aiming to get an analytics-ready column store that stays in sync automatically. The first run silently lost data: because replicas write their own position into InnoDB system tables alongside DuckDB data, every applied transaction spans two engines and triggers a two-phase commit, and a bug in the engine's prepare/commit logic dropped the DuckDB writes while reporting success. The fix landed in v0.2.3, after which INSERTs, UPDATEs, DELETEs, all column types, DDL, transactions, bulk loads, graceful restarts, and SIGKILL crash recovery all replicate correctly and match the primary byte-for-byte. The project remains an experiment, not production software, and is available under GPLv2 on GitHub.
Source: https://www.percona.com/blog/replicating-from-innodb-into-a-duckdb-storage-engine. 8 Sync News only summarizes and links out; content copyright belongs to the authors and original sources.
