Bug #99105 transaction_write_set_extraction requires binlog_format ROW

• Submitted: 30 Mar 2020 8:06
• Modified: 6 May 2020 9:37
• Reporter: Matthias Crauwels (OCA)
• Status: Closed
• Category: MySQL Server: Documentation
• Severity: S3 (Non-critical)
• Version: 8.0, 5.7
• OS: Any
• CPU Architecture: Any

[30 Mar 2020 8:06] Matthias Crauwels

Description:
Please include in the documentation of the transaction_write_set_extraction that this variable requires binlog_format = ROW to function

How to repeat:
mysql [localhost:8018] {msandbox} ((none)) > SELECT @@global.log_bin, @@global.binlog_format, @@global.transaction_write_set_extraction, @@version, @@version_comment;
+------------------+------------------------+-------------------------------------------+-----------+------------------------------+
| @@global.log_bin | @@global.binlog_format | @@global.transaction_write_set_extraction | @@version | @@version_comment            |
+------------------+------------------------+-------------------------------------------+-----------+------------------------------+
|                1 | STATEMENT              | OFF                                       | 8.0.18    | MySQL Community Server - GPL |
+------------------+------------------------+-------------------------------------------+-----------+------------------------------+
1 row in set (0.00 sec)

mysql [localhost:8018] {msandbox} ((none)) > SET GLOBAL transaction_write_set_extraction = XXHASH64;
ERROR 3099 (HY000): Cannot change the value of variable transaction_write_set_extraction without binary log format as ROW.
mysql [localhost:8018] {msandbox} ((none)) >

Suggested fix:
update docs

[30 Mar 2020 10:31] MySQL Verification Team

Hello Matthias,

Thank you for the report and feedback.

regards,
Umesh

[6 May 2020 9:37] Margaret Fisher

Posted by developer:
 
Thanks very much for pointing this out. I have corrected the omission.