[MXS-4821] Multi-statement detection works differently on non-AVX2 CPUs Created: 2023-10-20  Updated: 2023-10-25  Resolved: 2023-10-25

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 23.08.1
Fix Version/s: 23.08.2

Type: Bug Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Problem/Incident
causes MXS-4817 maxscale crashes on maxsimd::generic:... Closed

 Description   

While investigating MXS-4817, I found out that the handling of trailing END tokens is different between the AVX2 and the generic versions of the multi-statement detection code. The AVX2 version does not detect the trailing ends whereas the generic one does.

The behavior of the generic one is wrong as it also discards true multi-statement commands executed with BEGIN NOT ATOMIC. Thus, both this bug and MXS-4817 will be fixed by simply removing the detection from the generic version.
Generated at Thu Feb 08 04:31:24 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.