[MDEV-24617] OPTIMIZE on a sequence causes unexpected ER_BINLOG_UNSAFE_STATEMENT warning Created: 2021-01-18 Updated: 2022-08-24 Resolved: 2022-03-10 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Replication, Sequences |
| Affects Version/s: | 10.3, 10.4, 10.5, 10.6, 10.7 |
| Fix Version/s: | 10.3.35, 10.4.25, 10.5.16, 10.6.8, 10.7.4, 10.8.3 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Elena Stepanova | Assignee: | Andrei Elkin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | replication-statement-format-unsafe | ||
| Issue Links: |
|
||||||||
| Description |
|
OPTIMIZE TABLE on a sequence causes ER_BINLOG_UNSAFE_STATEMENT warning ("Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT"), even with binlog_format set to mixed or row.
|
| Comments |
| Comment by Andrei Elkin [ 2022-03-03 ] |
|
Brandon, could you please review the patch the soonest, as it is a support case. Thank you. Andrei |
| Comment by Brandon Nesterenko [ 2022-03-03 ] |
|
Approved after discussion and analysis on Slack looking into the completeness of CF_CAN_GENERATE_ROW_EVENTS and other use cases which set the variable share->non_determinstic_insert |