EC
3061
MariaDBWARNINGNotableReplicationHIGH confidence

Unsafe statement with full-text plugin in binlog

Production Risk

Medium — replication may diverge silently if warning is ignored.

What this means

A statement that uses a full-text parser plugin is unsafe for statement-based binary logging because the plugin may produce non-deterministic results.

Why it happens
  1. 1Using MATCH … AGAINST with a custom full-text plugin in STATEMENT binlog format.
  2. 2DML on a table with a full-text index backed by a third-party plugin.
How to reproduce
trigger — this will error
trigger — this will error
INSERT INTO articles SELECT * FROM src WHERE MATCH(body) AGAINST ('term');

expected output

Warning (Code 3061): Statement is unsafe because it uses a fulltext parser plugin which may not be safe to replicate.

Fix

Switch to ROW-based or MIXED binlog format

Switch to ROW-based or MIXED binlog format
SET GLOBAL binlog_format = 'ROW';

Why this works

ROW format replicates the actual row changes, avoiding non-determinism.

What not to do

✕

Sources
Official documentation ↗

MySQL 8.0 — 3061 ER_BINLOG_UNSAFE_FULLTEXT_PLUGIN4

Content generated with AI assistance and reviewed for accuracy. Found an error? hello@errcodes.dev

← All MariaDB errors