Issues Regarding the Modification of the binlog_format Parameter

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 关于binlog_format参数修改问题

| username: 健康的腰间盘

Currently, TiDB’s default binlog_format is STATEMENT. Using CloudCanal for data migration requires binlog_format to be ROW. I found a similar reference on the official website: TiDB Data Migration 任务前置检查 | PingCAP 文档中心. If this parameter is modified, what impact will it have on log backups? Will it cause the logs to become larger or create issues with BR restoration?

| username: xfworld | Original post link

Referring to the configuration of TICDC, CloudCanal should have instructions.

binlog_format is a compatibility configuration used for MySQL compatibility and has no practical significance for TICDC.

| username: 健康的腰间盘 | Original post link

I modified this parameter, does it have no actual impact on TiDB’s log backup?

| username: DBAER | Original post link

This is only compatible with the MySQL ecosystem, so it should be of no use for TiDB.

| username: 像风一样的男子 | Original post link

You chose TiDB as the database type.

| username: Miracle | Original post link

Yes, this parameter has no actual effect, TiDB only has ROW format.

| username: yytest | Original post link

Indeed, it’s all for MySQL compatibility.