[MDEV-4985] Correctly handle GTID event group for stand-alone multi-table ROW events Created: 2013-09-03  Updated: 2013-10-09  Resolved: 2013-10-09

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Kristian Nielsen Assignee: Kristian Nielsen
Resolution: Won't Fix Votes: 0
Labels: gtid


 Description   

When a statement is binlogged stand-alone (as opposed to bracketed by
BEGIN/COMMIT or BEGIN/XID), the GTID code needs to correctly detect the end of
the event group without the availability of COMMIT or XID.

In row-based binlogging with multi-table updates, multiple row events can be
logged in a single stand-alone event group. The last such row event has a
special flag that marks the end of the group.

The GTID code must correctly detect and act on this flag (currently it does
not).

 Comments   
Comment by Kristian Nielsen [ 2013-10-09 ]

As far as I could determine in the code, it is not actually possible to get a
stand-alone Rows_log_event in the binlog. It will always be bracketed by
GTID ... COMMIT/ROLLBACK/XID.

This makes this bug a non-issue - the event group will never be terminated by
a rows_log_event with the STMT_END_F set.

So it does not seem worth it to "fix" - it would involve passing in the byte
buffer containing the actual event, and locating the flag inside - all of
which will be dead code.

Generated at Thu Feb 08 07:00:46 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.