Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.2.44, 11.0.2, 10.3.39, 10.8.8, 10.4.30, 10.5.21, 10.6.14, 10.9.7, 10.10.5, 10.11.4, 10.7(EOL)
-
None
Description
I assume, for server with configuration
binlog-format=MIXED
binlog-row-image=FULL
there is an issue with non-full binary log representation for at least INSERT and UPDATE statements when "ON DUPLICATE KEY UPDATE" is used which was described in https://jira.mariadb.org/browse/MDEV-21810 and https://jira.mariadb.org/browse/MDEV-28310.
As far as I can see, examples from those tickets still produce non-full binary log result on checked 10.2 - 11.0 versions currently.
Attachments
Issue Links
- relates to
-
MDEV-21810 MBR: Unexpected "Unsafe statement" warning and use of non-full image with binlog_row_image=FULL
-
- Closed
-
-
MDEV-28310 Missing binlog data for INSERT .. ON DUPLICATE KEY UPDATE
-
- Closed
-
Thank you for the report!
I repeated the test case from
MDEV-21810, with binlog_row_image=FULL - not full image is generated, the part about warning was fixed10.4 7d968f8c8aaca01614dfb46
#230725 10:06:25 server id 1 end_log_pos 847 CRC32 0x92b5c0ed Annotate_rows:
#Q> INSERT INTO t1 (a,b) VALUES (1,20) ON DUPLICATE KEY UPDATE b = 30
#230725 10:06:25 server id 1 end_log_pos 894 CRC32 0x9078d8d8 Table_map: `test`.`t1` mapped to number 32
# at 894
#230725 10:06:25 server id 1 end_log_pos 946 CRC32 0x6feff097 Update_rows: table id 32 flags: STMT_END_F
BINLOG '
gYK/ZBMBAAAALwAAAH4DAAAAACAAAAAAAAEABHRlc3QAAnQxAAMDAwMAB9jYeJA=
gYK/ZBgBAAAANAAAALIDAAAAACAAAAAAAAEAA/8D/AEAAAAKAAAA/AEAAAAeAAAAl/Dvbw==
'/*!*/;
### UPDATE `test`.`t1`
### WHERE
### @1=1
### @2=10
### @3=NULL
### SET
### @1=1
### @2=30
# Number of rows: 1