AliSQL 8.0.44-3 — Binlog Realtime Replication and DuckDB updates
AliSQL 8.0.44-3 adds Binlog Realtime Replication (BRR), updates the embedded DuckDB to 1.5.2, and fixes integration issues. It remains based on MySQL 8.0.44.
Official GitHub release: AliSQL-8.0.44-3
Binlog realtime replication
BRR transmits eligible transaction-cache events before source commit. With early apply enabled, dedicated replica workers can execute supported DDL and large transactions ahead of the commit. Final completion still follows the source transaction outcome and GTID dependencies; BRR is not synchronous replication and does not guarantee zero lag.
- Source and replica negotiate a matching BRR protocol on the default replication channel.
- Large-transaction transmission requires
binlog_cache_free_flush=ONon the source, an eligible disk-backed cache, and no binlog transaction compression. The source-side size threshold defaults to 512 GiB, with a lower bound of 10 MiB. - Early apply requires GTIDs, parallel replication, nonzero
binlog_realtime_apply_workers,replica_preserve_commit_order=OFF, and the documented channel restrictions. - DDL early transmission has a default threshold of 1000 ms. Supported transactional ALTER/rebuild paths are eligible; instant DDL and replica-applier DDL are excluded.
- New Information Schema tables
BRR_SOURCE_TRX_INFO,BRR_SENDER_TRX_INFO, andBRR_REPLICA_INFO, plus status counters, expose active BRR work.
See the Binlog Realtime Replication guide for setup, monitoring, restrictions, and fallback behavior.
DuckDB updates
The embedded source is upgraded to DuckDB 1.5.2.
- Optional AUTO_INCREMENT support for DuckDB tables, including dictionary, DDL, and replication handling.
- Optional background automatic checkpoints with a configurable interval between full checkpoints.
JSON_OBJECTAGG, additional temporal/string SQL compatibility, and cross-schemaRENAME TABLE.- Fixes for quoting, NOT NULL changes, generated-column dependencies, partition operations, startup metadata-lock deadlocks, rollback exceptions, and failed atomic cross-engine DDL.
Defaults and upgrade notes
| Feature | Default |
|---|---|
| BRR source and receiver switches | OFF |
| BRR early-apply workers | binlog_realtime_apply_workers=0 |
| DuckDB engine mode | duckdb_mode=NONE |
| DuckDB AUTO_INCREMENT | duckdb_support_auto_increment=OFF |
| Background checkpoints | duckdb_enable_background_checkpoint=OFF |
| Full-checkpoint interval | duckdb_background_checkpoint_full_interval=0 |
The three new DuckDB variables are global and dynamic. A full-checkpoint interval of 0 means every background checkpoint is full when background mode is enabled.
DuckDB Multi-Trx Batch requires replica_parallel_workers=0. BRR early apply requires parallel workers, so these settings cannot be combined unchanged. BRR uses Free Flush cache files; active DuckDB mode still selects a dedicated commit path. Review the version-pinned guides before enabling either mode.
Integration fixes address skipped BRR metadata-event memory leaks, startup XA recovery metadata locking, and normal binlogging/GTID generation for partially successful multi-table OPTIMIZE when early binlogging is disabled.
Packages and image
The official release provides these Linux binary packages for glibc 2.17:
| Platform | Download |
|---|---|
| Linux x86_64 | alisql-8.0.44-3-linux-glibc2.17-x86_64.tar.xz |
| Linux aarch64 | alisql-8.0.44-3-linux-glibc2.17-aarch64.tar.xz |
The release also lists songhuaxiong/alisql:8.0.44-3 for linux/amd64 and linux/arm64. The image build follows publication of both binary packages; check the linked build status before using it.