Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
6.4.14, 22.08.11, 23.02.8, 23.08.5
-
None
-
MXS-SPRINT-205, MXS-SPRINT-206
Description
If a query that modifies the session state is executed using the binary protocol (i.e. COM_STMT_PREPARE), the history replay will not apply that state change. The COM_STMT_PREPARE is correctly prepared but the effects of it won't take effect until a follow-up COM_STMT_EXECUTE is done.
With MariaDB, this is as simple as appending a COM_STMT_EXECUTE with an ID of -1 after the COM_STMT_PREPARE for any command that modifies the session state. For MySQL, this extension is not (AFAIK) available and cannot be used to solve the problem.