Bug #73744 rbr_exec_mode is not documented
| Submitted: | 27 Aug 2014 16:24 | Modified: | 10 Oct 2014 16:06 |
|---|---|---|---|
| Reporter: | Jaime Crespo (OCA) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
| Version: | 5.7 | OS: | Any |
| Assigned to: | David Moss | CPU Architecture: | Any |
[27 Aug 2014 16:24]
Jaime Crespo
[27 Aug 2014 18:27]
MySQL Verification Team
Thank you for the bug report.
[10 Oct 2014 16:06]
David Moss
Thanks for your feedback, this is now documented as follows: rbr_exec_mode This variable switches the server between IDEMPOTENT mode and STRICT mode. IDEMPOTENT mode causes suppression of duplicate-key and no-key-found errors. This mode is useful when replaying a row-based binary log on a server that causes conflicts with existing data. mysqlbinlog uses this mode when you set the --idempotent option by writing the following to the output: SET SESSION RBR_EXEC_MODE=IDEMPOTENT;
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.038 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.